AWS CodePipeline聽vs聽Jenkins

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

AWS CodePipeline

+ 1

+ 1
Add tool

AWS CodePipeline vs Jenkins: What are the differences?

What is AWS CodePipeline? Continuous delivery service for fast and reliable application updates. CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.

What is Jenkins? 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.

AWS CodePipeline can be classified as a tool in the "Continuous Deployment" category, while Jenkins is grouped under "Continuous Integration".

Some of the features offered by AWS CodePipeline are:

  • Workflow Modeling
  • AWS Integrations
  • Pre-Built Plugins

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

  • Easy installation
  • Easy configuration
  • Change set support

"Simple to set up" is the top reason why over 3 developers like AWS CodePipeline, while over 497 developers mention "Hosted internally" as the leading cause for choosing Jenkins.

Jenkins is an open source tool with 13.2K GitHub stars and 5.43K GitHub forks. Here's a link to Jenkins's open source repository on GitHub.

According to the StackShare community, Jenkins has a broader approval, being mentioned in 1753 company stacks & 1479 developers stacks; compared to AWS CodePipeline, which is listed in 30 company stacks and 15 developer stacks.

Advice on AWS CodePipeline and Jenkins
Needs advice
Azure 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)

If your source code is on GitHub, also take a look at Github actions.

See more
Mohammad Hossein Amri
Chief Technology Officer at Axceligent Solutions | 3 upvotes 路 167.2K views
Needs advice

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 路 154.6K views

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

See more
Needs advice

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 路 73.2K views

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
Decisions about AWS CodePipeline and Jenkins
Stephen Badger | Vital Beats
Senior DevOps Engineer at Vital Beats | 2 upvotes 路 65.9K 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
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of AWS CodePipeline
Pros of Jenkins
  • 13
    Simple to set up
  • 8
    Managed service
  • 4
    GitHub integration
  • 3
    Parallel Execution
  • 2
    Automatic deployment
  • 0
    Manual Steps Available
  • 521
    Hosted internally
  • 463
    Free open source
  • 313
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 208
    Rich set of plugins with good documentation
  • 108
    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
    Great flexibility
  • 8
    Git and Maven integration is better
  • 7
    Continuous Integration
  • 6
    Github integration
  • 6
    Slack Integration (plugin)
  • 5
    100% free and open source
  • 5
    Self-hosted GitLab Integration (plugin)
  • 5
    Easy customisation
  • 4
    Docker support
  • 3
    Pipeline API
  • 3
    Excellent docker integration
  • 3
    Platform idnependency
  • 3
    Fast builds
  • 2
    Hosted Externally
  • 2
    It`w worked
  • 2
    Can be run as a Docker container
  • 2
  • 2
    AWS Integration
  • 2
    It's Everywhere
  • 2
  • 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 AWS CodePipeline
Cons of Jenkins
  • 2
    No project boards
  • 1
    No integration with "Power" 365 tools
  • 12
    Workarounds needed for basic requirements
  • 8
    Groovy with cumbersome syntax
  • 6
    Plugins compatibility issues
  • 6
    Limited abilities with declarative pipelines
  • 5
    Lack of support
  • 4
    No YAML syntax
  • 2
    Too tied to plugins versions

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is AWS CodePipeline?

CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.

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!

What companies use AWS CodePipeline?
What companies use Jenkins?
See which teams inside your own company are using AWS CodePipeline or Jenkins.
Sign up for Private StackShareLearn More

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

What tools integrate with AWS CodePipeline?
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


Dec 4 2019 at 8:01PM


What are some alternatives to AWS CodePipeline and Jenkins?
AWS CodeDeploy
AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications.
AWS CodeBuild
AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don鈥檛 need to provision, manage, and scale your own build servers.
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.
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
AWS CodeStar
Start new software projects on AWS in minutes using templates for web applications, web services and more.
See all alternatives
How developers use AWS CodePipeline and Jenkins
Kalibrr uses

All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.

Wirkn Inc. uses

Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.

B霉i Thanh uses
  • Continuous Deploy
  • Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
  • Staging and production stages: Build and rollback quicly with Ansistrano playbook
  • Sending messages of job results to Chatwork.
AngeloR uses

Currently serves as the location that our QA team builds various automated testing jobs.

At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.

Trusted Shops GmbH uses

We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.