StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Jenkins vs Visual Studio App Center

Jenkins vs Visual Studio App Center

OverviewDecisionsComparisonAlternatives

Overview

Jenkins
Jenkins
Stacks59.2K
Followers50.4K
Votes2.2K
GitHub Stars24.6K
Forks9.2K
Visual Studio App Center
Visual Studio App Center
Stacks113
Followers232
Votes4

Jenkins vs Visual Studio App Center: What are the differences?

Introduction

Jenkins and Visual Studio App Center are popular Continuous Integration/Continuous Deployment (CI/CD) tools that are used in software development to automate the build, test, and deployment processes. While both tools aim to streamline the development and release workflows, there are key differences between Jenkins and Visual Studio App Center.

  1. Integration with Development Tools: One major difference between Jenkins and Visual Studio App Center is their integration with development tools. Jenkins is highly configurable and can integrate with a wide range of development tools and technologies, making it a versatile choice for various projects. On the other hand, Visual Studio App Center is specifically designed to integrate seamlessly with the Microsoft development ecosystem, making it an ideal choice for projects developed using Microsoft technologies such as .NET and Xamarin.

  2. Platform Support: Another key difference lies in the platform support offered by Jenkins and Visual Studio App Center. Jenkins is an open-source tool that can be installed on almost any operating system, including Windows, macOS, and Linux. It also offers extensive support for a wide range of programming languages and software platforms. In contrast, Visual Studio App Center is a cloud-based service provided by Microsoft and is primarily focused on native and mobile app development. It offers robust support for iOS, Android, Xamarin, and React Native platforms, making it an excellent choice for mobile app development projects.

  3. Deployment Options: Both Jenkins and Visual Studio App Center support various deployment options, but they differ in terms of their native capabilities. Jenkins provides a wide range of plugins and extensions that allow developers to configure and customize their deployment pipelines as per their requirements. It supports various deployment methods, including FTP, SSH, and containerization tools like Docker. In contrast, Visual Studio App Center offers in-built support for app distribution, beta testing, and release management for mobile app platforms. It simplifies the deployment process for mobile apps and provides a centralized platform for managing app versions and releases.

  4. User Interface and Ease of Use: Jenkins is known for its highly customizable user interface, which allows developers to create and configure their CI/CD pipelines using a web-based interface or by writing code (Jenkinsfile). While this flexibility is beneficial for experienced users, it can be overwhelming for beginners. Visual Studio App Center, on the other hand, provides a more user-friendly and intuitive user interface that makes it easier for developers to set up and manage their CI/CD processes without the need for extensive configuration.

  5. Scalability and Infrastructure Management: Jenkins is a self-hosted tool, which means that it requires manual setup and maintenance of the infrastructure to run and scale the Jenkins server. It provides flexibility in terms of choosing the hardware, network, and storage configurations based on project requirements. Visual Studio App Center, being a cloud-based service, eliminates the need for infrastructure management as the hosting and scaling are handled by Microsoft. It offers a scalable and reliable infrastructure that can handle large-scale CI/CD workflows without the need for manual intervention.

  6. Community and Support: Jenkins has a large and active community of users and contributors, which results in a vast array of plugins, extensions, tutorials, and community support available online. With its open-source nature, Jenkins benefits from continuous improvements and enhancements driven by the community. Visual Studio App Center, being a proprietary tool, has a smaller user community. However, it offers dedicated technical support from Microsoft, ensuring reliable assistance in case of any issues or challenges faced during the development and deployment process.

In summary, the key differences between Jenkins and Visual Studio App Center lie in their integration with development tools, platform support, deployment options, user interface, ease of use, scalability, infrastructure management, and community support. Depending on the project requirements, developers can choose between the versatility and extensive customization options offered by Jenkins or the seamless integration with the Microsoft development ecosystem and mobile app-specific features provided by Visual Studio App Center.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Jenkins, Visual Studio App Center

Balaramesh
Balaramesh

Apr 20, 2020

Needs adviceonAzure PipelinesAzure Pipelines.NET.NETJenkinsJenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k
Comments
StackShare
StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k
Comments
Tatiana
Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k
Comments

Detailed Comparison

Jenkins
Jenkins
Visual Studio App Center
Visual Studio App Center

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Automate the lifecycle of your iOS, Android, Windows, and macOS apps. Connect your repo and within minutes build in the cloud, test on thousands of real devices, distribute to beta testers and app stores, and monitor real-world usage with crash and analytics data. All in one place.

Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support
Build; Test; Distribute; Crashes; Diagnostics; Analytics; Push; CD/CI;
Statistics
GitHub Stars
24.6K
GitHub Stars
-
GitHub Forks
9.2K
GitHub Forks
-
Stacks
59.2K
Stacks
113
Followers
50.4K
Followers
232
Votes
2.2K
Votes
4
Pros & Cons
Pros
  • 523
    Hosted internally
  • 469
    Free open source
  • 318
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 211
    Rich set of plugins with good documentation
Cons
  • 13
    Workarounds needed for basic requirements
  • 10
    Groovy with cumbersome syntax
  • 8
    Plugins compatibility issues
  • 7
    Lack of support
  • 7
    Limited abilities with declarative pipelines
Pros
  • 1
    Slack integration
  • 1
    Show error issues for mobile devices
  • 1
    Bug tracking integration
  • 1
    For Mobile apps diagnostics and tracking
Integrations
No integrations available
GitHub
GitHub
Bitbucket
Bitbucket
Azure DevOps
Azure DevOps
Slack
Slack

What are some alternatives to Jenkins, Visual Studio App Center?

Ionic

Ionic

Free and open source, Ionic offers a library of mobile and desktop-optimized HTML, CSS and JS components for building highly interactive apps. Use with Angular, React, Vue, or plain JavaScript.

Travis CI

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

Flutter

Flutter

Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android.

React Native

React Native

React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native.

CircleCI

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

Xamarin

Xamarin

Xamarin’s Mono-based products enable .NET developers to use their existing code, libraries and tools (including Visual Studio*), as well as skills in .NET and the C# programming language, to create mobile applications for the industry’s most widely-used mobile devices, including Android-based smartphones and tablets, iPhone, iPad and iPod Touch.

NativeScript

NativeScript

NativeScript enables developers to build native apps for iOS, Android and Windows Universal while sharing the application code across the platforms. When building the application UI, developers use our libraries, which abstract the differences between the native platforms.

TeamCity

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot