Need advice about which tool to choose?Ask the StackShare community!

Azure DevOps

2.7K
2.8K
+ 1
249
Jenkins

58.2K
49.6K
+ 1
2.2K
Add tool

Azure DevOps vs Jenkins: What are the differences?

Azure DevOps and Jenkins are two popular tools used for automated software development and deployment. While they share some similarities, there are key differences that set them apart. Let's discuss the key differences between them.

  1. Integration with Microsoft Tools and Services: Azure DevOps is tightly integrated with various Microsoft tools and services, such as Azure cloud services, Visual Studio, and Active Directory. This allows seamless collaboration and integration within the Microsoft ecosystem. On the other hand, Jenkins is a more flexible tool and can integrate with a wide range of third-party tools and services, making it suitable for diverse development environments.

  2. Deployment Options: Azure DevOps provides a cloud-based solution, allowing users to host and manage their pipelines and repositories on the Azure platform. It also provides built-in support for deploying applications to Azure cloud services. In contrast, Jenkins offers more deployment flexibility as it can be installed on-premises or in any cloud environment. This makes Jenkins a preferred choice for organizations that require complete control over their infrastructure and deployment pipelines.

  3. Out-of-the-box Functionality: Azure DevOps offers a comprehensive set of integrated features, including version control, continuous integration (CI), continuous delivery (CD), and testing tools. These features are readily available and do not require extensive configuration. Jenkins, on the other hand, provides a more customizable approach, allowing users to define and configure their own CI/CD pipelines using plugins. This flexibility gives users more control over the pipeline setup but also requires more time and effort for initial setup and maintenance.

  4. Ease of Use: Azure DevOps provides a user-friendly web-based interface, making it relatively easy to set up and use. It provides a step-by-step guided experience for creating pipelines and managing projects. Jenkins, on the other hand, has a steeper learning curve, especially for users who are not familiar with its configuration and scripting concepts. While Jenkins provides a powerful and flexible platform, it requires a higher level of technical expertise to set up and maintain.

  5. Scalability: Azure DevOps is designed to scale seamlessly, allowing users to handle large projects and distributed teams with ease. It provides features like parallel execution, agent pools, and scalability in the cloud. Jenkins can also handle large-scale projects, but it requires more manual configuration and management to ensure optimal performance. Users need to set up their own distributed build infrastructure and manage resources effectively to achieve scalability in Jenkins.

  6. Pricing Model: Azure DevOps offers different pricing options, including a free tier for small teams and pay-as-you-go plans for larger organizations. It provides transparent pricing based on the number of users and usage. Jenkins, on the other hand, is an open-source tool that is free to use. However, organizations using Jenkins need to invest in infrastructure, maintenance, and support, which can add to the overall cost.

In summary, Azure DevOps provides seamless integration with Microsoft tools and services, offers a cloud-based deployment option, and has out-of-the-box functionality with a user-friendly interface. On the other hand, Jenkins offers more flexibility, customizable pipelines, ease of scalability, and a free pricing model.

Advice on Azure DevOps and Jenkins
Needs advice
on
Azure PipelinesAzure Pipelines
and
JenkinsJenkins

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.

See more
Replies (1)
Recommends
on
GitHubGitHub

If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions

See more
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 517.7K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 500.5K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Needs advice
on
ConcourseConcourse
and
JenkinsJenkins

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 419.6K views
Recommends
on
ConcourseConcourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

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?"

See more
Replies (6)
Dustin Falgout
Senior Developer at Elegant Themes · | 13 upvotes · 574K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit · | 9 upvotes · 887.5K views
Recommends
on
Travis CITravis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more
Recommends
on
Google Cloud BuildGoogle Cloud Build

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
on
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
on
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
on
BuildkiteBuildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about Azure DevOps and Jenkins

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.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Azure DevOps
Pros of Jenkins
  • 56
    Complete and powerful
  • 32
    Huge extension ecosystem
  • 27
    Azure integration
  • 26
    Flexible and powerful
  • 26
    One Stop Shop For Build server, Project Mgt, CDCI
  • 15
    Everything I need. Simple and intuitive UI
  • 13
    Support Open Source
  • 8
    Integrations
  • 7
    GitHub Integration
  • 6
    Cost free for Stakeholders
  • 6
    One 4 all
  • 6
    Crap
  • 6
    Project Mgmt Features
  • 5
    Runs in the cloud
  • 3
    Agent On-Premise(Linux - Windows)
  • 2
    Aws integration
  • 2
    Link Test Cases to Stories
  • 2
    Jenkins Integration
  • 1
    GCP Integration
  • 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
  • 111
    Has support for build pipelines
  • 68
    Easy setup
  • 66
    It is open-source
  • 53
    Workflow plugin
  • 13
    Configuration as code
  • 12
    Very powerful tool
  • 11
    Many Plugins
  • 10
    Continuous Integration
  • 10
    Great flexibility
  • 9
    Git and Maven integration is better
  • 8
    100% free and open source
  • 7
    Github integration
  • 7
    Slack Integration (plugin)
  • 6
    Easy customisation
  • 6
    Self-hosted GitLab Integration (plugin)
  • 5
    Docker support
  • 5
    Pipeline API
  • 4
    Fast builds
  • 4
    Platform idnependency
  • 4
    Hosted Externally
  • 4
    Excellent docker integration
  • 3
    It`w worked
  • 3
    Customizable
  • 3
    Can be run as a Docker container
  • 3
    It's Everywhere
  • 3
    JOBDSL
  • 3
    AWS Integration
  • 2
    Easily extendable with seamless integration
  • 2
    PHP Support
  • 2
    Build PR Branch Only
  • 2
    NodeJS Support
  • 2
    Ruby/Rails Support
  • 2
    Universal controller
  • 2
    Loose Coupling

Sign up to add or upvote prosMake informed product decisions

Cons of Azure DevOps
Cons of Jenkins
  • 8
    Still dependant on C# for agents
  • 5
    Half Baked
  • 5
    Many in devops disregard MS altogether
  • 4
    Not a requirements management tool
  • 4
    Jack of all trades, master of none
  • 4
    Capacity across cross functional teams not visibile
  • 3
    Poor Jenkins integration
  • 2
    Tedious for test plan/case creation
  • 1
    Switching accounts is impossible
  • 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
  • 5
    No YAML syntax
  • 4
    Too tied to plugins versions

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Azure DevOps?

Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.

What is Jenkins?

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.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Azure DevOps and Jenkins as a desired skillset
What companies use Azure DevOps?
What companies use Jenkins?
Manage your open source components, licenses, and vulnerabilities
Learn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Azure DevOps?
What tools integrate with Jenkins?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Mar 24 2021 at 12:57PM

Pinterest

GitJenkinsKafka+7
3
2190
GitJenkinsGroovy+4
4
2755
Dec 4 2019 at 8:01PM

Pinterest

KubernetesJenkinsTensorFlow+4
5
3319
GitGitHubPython+22
17
14265
JavaScriptGitHubPython+42
53
22081
What are some alternatives to Azure DevOps and Jenkins?
GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
AWS CodePipeline
CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.
Jira
Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster.
Visual Studio
Visual Studio is a suite of component-based software development tools and other technologies for building powerful, high-performance applications.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
See all alternatives