Likelihood to Recommend I think AWS CodePipeline is a great tool for anyone wanted automated deployments in a multi-server/container AWS environment. AWS also offers services like Elastic Beanstalk that provide a more managed hosting & deployment experience. CodePipeline is a good middle ground with solid, built-in automation with enough customizability to not lock people into one deployment or architecture philosophy.
Read full review If you value integration over cost, Bamboo is clearly the way to go. It offers tight integration to the rest of the Atlassian suite, and when you need traceability from issue to build, Atlassian is the right way to go. However, if you find yourself needing to save on costs, you may consider taking an approach of rolling your own build system with open source alternatives, such as
Jenkins , if you don't [mind] putting in a little extra elbow grease.
Read full review Pros It is reliable and works without errors It integrates well with our repository and all other AWS functions as well as our end database Read full review Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately. Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well. Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful. Read full review Cons Ease of use - things like CircleCI or other tools are a bit easier to learn. Ability to build from more sources. Read full review Extremely hard barrier to entry for non-backend developers Blackbox makes it hard to customize functionality The inability to add features without breaking core functionality No cloud solution Tasks cannot be put in if/else statements No clear right way to form build plans Read full review Usability Overall, I give AWS Codepipeline a 9 because it gets the job done and I can't complain much about the web interface as much of the action is taking place behind the scenes on the terminal locally or via Amazon's infrastructure anyway. It would be nicer to have a better flowing and visualizable web interface, however.
Read full review Bamboo was fairly easy to navigate but in the end it always felt as if it was developed as a bolt-on and not a true group up user interface. There were multiple ways to get to everything and the path was never the same. So it was difficult for users to really get a feel of how to use the application.
Read full review Performance Our pipeline takes about 30 minutes to run through. Although this time depends on the applications you are using on either end, I feel that it is a reasonable time to make upgrades and updates to our system as it is not an every day push.
Read full review Support Rating We didn't need a lot of support with AWS CodePipeline as it was pretty straightforward to configure and use, but where we ran into problems, the AWS community was able to help. AWS support agents were also helpful in resolving some of the minor issues we encountered, which we could not find a solution elsewhere.
Read full review Support for Bamboo has started lack a little over the years. Atlassian has been moving more towards
Bitbucket Pipelines and away from the on-premise install of Bamboo. While the tool is still great, it may take a little bit of time to get a question answered by official support.
Read full review Alternatives Considered CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for
Beanstalk , which is often used as a deployment target in relation to CodePipeline.
CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via
Beanstalk .
Jenkins is open source and not a native AWS service, that is its primary differentiator.
Jenkins can also be used as a supplement to CodePipeline.
Read full review We selected Bamboo because its capabilities to integrate with other
Atlassian products specially
Jira Software ,
Bitbucket and in some useful scenarios with
Confluence . Also, we found these pros important for us: great user interface, easily agent deployment, Docker compability, simply to maintain / manage, and straightforwardly integration with different notification platforms
Read full review Return on Investment CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing. CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch. CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually. Read full review It helped us achieve the Continuous Deployment and Continuous Integration goals for our applications, a huge milestone that saved a lot of time for developers in making the builds and deployments and saved time for QA in running the automated tests. Helped with DevOps: we moved the formal approval from the email to the system and allowed the approver to actually push the button for the production deployments. Biggest positive impact of using Bamboo is that it improved our response time to customers and increased the frequency of our deliveries to them. Read full review ScreenShots