What are the pros and cons of using AWS CodePipeline vs Jenkins
What are the pros and cons of using AWS CodePipeline vs Jenkins?
I can't see a whole lot of info on the interwebs (apart from https://stackshare.io/stackups/jenkins-vs-aws-codepipeline). As far as I can see they are as follows:
AWS CodePipeline Pros
- Web-based
- integrated with AWS
- simple to setup (as web-based)
AWS CodePipeline Cons
- can't be used to set up code repos locally
Jenkins Pros
- standalone software
- can be used for many systems (other than AWS)
- many options for setup (e.g. plugins)
- can be used to setup code repos locally
Any other major differences that people can use to make an informed choice?
Answer
Other downside of using AWS CodePipeLine is lack of integration with source control providers other than GitHub. The only other option we have is to create version enabled Amazon S3 bucket and push our code there. This creates an extra layer between Source control and CodePipeline.
Also, there is no proper documentation available to explain how one could push their code to Amazon S3 bucket for codebases built in commonly used platforms such as .Net. The example given in AWS website deals with some random files which is not helpful whatsoever.
The other entry(trivial?) missing in your question from cons section of AWS CodePipeLine is, Price. Jenkins is free. Gitlab SCM solution is now provided by AWS https://aws.amazon.com/blogs/devops/integrating-git-with-aws-codepipeline/