Overview

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

Azure Pipelines

Stacks2.3K

Followers457

Votes14

Azure Pipelines vs Jenkins: What are the differences?

Introduction

Azure Pipelines and Jenkins are both popular continuous integration and continuous delivery (CI/CD) tools used in software development. While they serve similar purposes, there are key differences between them that make them more suitable for specific scenarios.

Integration with Azure services: Azure Pipelines is a fully integrated CI/CD solution provided by Microsoft Azure. It provides seamless integration with other Azure services such as Azure DevOps, Azure Repos, and Azure Artifacts. This makes it an excellent choice for organizations already using Azure services in their development processes. Jenkins, on the other hand, is an open-source tool that requires manual configuration and integration with external services.
Ease of setup and maintenance: Azure Pipelines offers a cloud-based solution that requires minimal setup and maintenance effort. It automatically scales to meet the needs of your development projects, eliminating the need for resource management. Jenkins, being a self-hosted tool, requires manual installation, configuration, and ongoing maintenance of infrastructure resources. This can be time-consuming and resource-intensive, especially for smaller development teams.
Pipeline as code: Azure Pipelines supports pipeline configuration using the YAML syntax, also known as "pipeline as code". YAML allows developers to version control the pipeline configuration along with the source code, making it easier to manage and track changes over time. Jenkins, though it offers some support for pipeline definition using plugins like Jenkinsfile, does not provide a native and standardized approach for pipeline as code.
Extensibility and plugin ecosystem: Jenkins has a vast plugin ecosystem, with thousands of plugins available for extending its functionality. This makes it highly customizable and adaptable to various development environments. Azure Pipelines, though it also supports extensions and integrations, has a more limited selection of available extensions compared to Jenkins.
Cost: Azure Pipelines offers a generous free tier for public projects and provides usage-based pricing for private projects. The cost is directly linked to the usage of Azure resources. Jenkins, being a self-hosted tool, requires the allocation of infrastructure resources, which can involve additional costs for hardware, maintenance, and upgrades.
Community and support: Jenkins has a large and active community of users and contributors, providing ample resources for documentation, tutorials, and troubleshooting. Azure Pipelines, being a product of Microsoft, benefits from the support of the Microsoft Azure community and Microsoft's technical expertise. Microsoft offers comprehensive documentation, tutorials, and support options, making it a reliable choice for enterprises requiring extensive support.

In summary, Azure Pipelines offers seamless integration with Azure services, requires minimal setup and maintenance effort, supports pipeline as code, has a more limited selection of extensions compared to Jenkins, provides cost benefits with its usage-based pricing model, and benefits from the support of Microsoft's technical expertise. Jenkins, on the other hand, requires manual configuration and maintenance, has a vast plugin ecosystem for extensibility, incurs costs for infrastructure resources, and has an active community providing extensive resources for support.

🔥 Trending in Continuous Integration on StackShare

Everdone Continuous Integration

Everdone

Try it View Docs Alternatives

Try

0

1

Advice on Jenkins, Azure Pipelines

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

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

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

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	Azure Pipelines
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.	Fast builds with parallel jobs and test execution. Use container jobs to create consistent and reliable builds with the exact tools you need. Create new containers with ease and push them to any registry.
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	Any language, any platform; Containers and Kubernetes; Extensible; Deploy to any cloud; Open source; Advanced workflows and features
Statistics
GitHub Stars 24.6K	GitHub Stars -
GitHub Forks 9.2K	GitHub Forks -
Stacks 59.2K	Stacks 2.3K
Followers 50.4K	Followers 457
Votes 2.2K	Votes 14
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 Limited abilities with declarative pipelines 7 Lack of support	Pros 4 Easy to get started 3 Unlimited CI/CD minutes 3 Built by Microsoft 2 Docker support 2 Yaml support
Integrations
No integrations available	.NET Core Slack Python Ruby Kubernetes .NET Node.js Linux Microsoft Azure RxJava

What are some alternatives to Jenkins, Azure Pipelines?

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 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.

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.

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 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.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.