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.
What is AWS CodePipeline?
What is Jenkins?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using AWS CodePipeline?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
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.
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.
- 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.
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.