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

Docker

112.6K
92.1K
+ 1
3.8K
Jenkins

43.3K
35.9K
+ 1
2.2K
Add tool

Docker vs Jenkins: What are the differences?

Developers describe Docker as "Enterprise Container Platform for High-Velocity Innovation". The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere. On the other hand, Jenkins is detailed as "An extendable open source continuous integration server". 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.

Docker and Jenkins are primarily classified as "Virtual Machine Platforms & Containers" and "Continuous Integration" tools respectively.

Some of the features offered by Docker are:

  • Integrated developer tools
  • open, portable images
  • shareable, reusable apps

On the other hand, Jenkins provides the following key features:

  • Easy installation
  • Easy configuration
  • Change set support

"Rapid integration and build up", "Isolation" and "Open source" are the key factors why developers consider Docker; whereas "Hosted internally", "Free open source" and "Great to build, deploy or launch anything async" are the primary reasons why Jenkins is favored.

Docker and Jenkins are both open source tools. It seems that Docker with 53.8K GitHub stars and 15.5K forks on GitHub has more adoption than Jenkins with 13.2K GitHub stars and 5.43K GitHub forks.

Lyft, StackShare, and Shopify are some of the popular companies that use Docker, whereas Jenkins is used by Instacart, Lyft, and Twitch. Docker has a broader approval, being mentioned in 3470 company stacks & 3322 developers stacks; compared to Jenkins, which is listed in 1753 company stacks and 1479 developer stacks.

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

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
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 Axceligent Solutions · | 3 upvotes · 246.1K views
Needs advice
on
JenkinsJenkins
and
GoCDGoCD

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 · 229.2K views

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

See more
Needs advice
on
JenkinsJenkins
and
ConcourseConcourse

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 · 146K views
Recommends
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
Developer at Elegant Themes · | 13 upvotes · 259.8K 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 · 238.8K views
Recommends
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

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
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
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
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 Docker and Jenkins
Kirill Mikhailov

Jenkins is a friend of mine. 😀

There are not much space for Jenkins competitors for now from my point of view. With declarative pipelines now in place, its super easy to maintain them and create new ones(altho I prefer scripted still). Self-hosted, free, huge community makes it the top choice so honestly for me it was an easy pick.

See more
Stephen Badger | Vital Beats
Senior DevOps Engineer at Vital Beats · | 2 upvotes · 101K views

Within our deployment pipeline, we have a need to deploy to multiple customer environments, and manage secrets specifically in a way that integrates well with AWS, Kubernetes Secrets, Terraform and our pipelines ourselves.

Jenkins offered us the ability to choose one of a number of credentials/secrets management approaches, and models secrets as a more dynamic concept that GitHub Actions provided.

Additionally, we are operating Jenkins within our development Kubernetes cluster as a kind of system-wide orchestrator, allowing us to use Kubernetes pods as build agents, avoiding the ongoing direct costs associated with GitHub Actions minutes / per-user pricing. Obviously as a consequence we take on the indirect costs of maintain Jenkins itself, patching it, upgrading etc. However our experience with managing Jenkins via Kubernetes and declarative Jenkins configuration has led us to believe that this cost is small, particularly as the majority of actual building and testing is handled inside docker containers and Kubernetes, alleviating the need for less supported plugins that may make Jenkins administration more difficult.

See more

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
Florian Sager
IT DevOp at Agitos GmbH · | 2 upvotes · 213K views
Chose
LXDLXD
over
DockerDocker

lxd/lxc and Docker aren't congruent so this comparison needs a more detailed look; but in short I can say: the lxd-integrated administration of storage including zfs with its snapshot capabilities as well as the system container (multi-process) approach of lxc vs. the limited single-process container approach of Docker is the main reason I chose lxd over Docker.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Docker
Pros of Jenkins
  • 821
    Rapid integration and build up
  • 688
    Isolation
  • 517
    Open source
  • 505
    Testa­bil­i­ty and re­pro­ducibil­i­ty
  • 459
    Lightweight
  • 217
    Standardization
  • 182
    Scalable
  • 105
    Upgrading / down­grad­ing / ap­pli­ca­tion versions
  • 86
    Security
  • 84
    Private paas environments
  • 33
    Portability
  • 25
    Limit resource usage
  • 15
    I love the way docker has changed virtualization
  • 15
    Game changer
  • 12
    Fast
  • 11
    Concurrency
  • 7
    Docker's Compose tools
  • 4
    Fast and Portable
  • 4
    Easy setup
  • 4
    Because its fun
  • 3
    Makes shipping to production very simple
  • 2
    It's dope
  • 1
    Highly useful
  • 1
    MacOS support FAKE
  • 1
    Its cool
  • 1
    Docker hub for the FTW
  • 1
    Very easy to setup integrate and build
  • 1
    Package the environment with the application
  • 1
    Does a nice job hogging memory
  • 1
    Open source and highly configurable
  • 1
    Simplicity, isolation, resource effective
  • 521
    Hosted internally
  • 465
    Free open source
  • 314
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 210
    Rich set of plugins with good documentation
  • 109
    Has support for build pipelines
  • 72
    Open source and tons of integrations
  • 63
    Easy setup
  • 61
    It is open-source
  • 54
    Workflow plugin
  • 11
    Configuration as code
  • 10
    Very powerful tool
  • 9
    Many Plugins
  • 8
    Continuous Integration
  • 8
    Great flexibility
  • 8
    Git and Maven integration is better
  • 6
    Github integration
  • 6
    100% free and open source
  • 6
    Slack Integration (plugin)
  • 5
    Easy customisation
  • 5
    Self-hosted GitLab Integration (plugin)
  • 4
    Docker support
  • 3
    Excellent docker integration
  • 3
    Platform idnependency
  • 3
    Fast builds
  • 3
    Pipeline API
  • 2
    Customizable
  • 2
    Can be run as a Docker container
  • 2
    It`w worked
  • 2
    JOBDSL
  • 2
    Hosted Externally
  • 2
    It's Everywhere
  • 2
    AWS Integration
  • 1
    NodeJS Support
  • 1
    PHP Support
  • 1
    Ruby/Rails Support
  • 1
    Universal controller
  • 1
    Easily extendable with seamless integration
  • 1
    Build PR Branch Only

Sign up to add or upvote prosMake informed product decisions

Cons of Docker
Cons of Jenkins
  • 7
    New versions == broken features
  • 5
    Documentation not always in sync
  • 5
    Unreliable networking
  • 3
    Moves quickly
  • 2
    Not Secure
  • 12
    Workarounds needed for basic requirements
  • 8
    Groovy with cumbersome syntax
  • 6
    Limited abilities with declarative pipelines
  • 6
    Plugins compatibility issues
  • 5
    Lack of support
  • 4
    No YAML syntax
  • 2
    Too tied to plugins versions

Sign up to add or upvote consMake informed product decisions