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 IBM UrbanCode Deploy is excellent for code deployments such as Java, .Net, C++, etc. It can also deploy and run SQLs reasonably well. Where it lacks is the ability for executables, Jars, WARs, EARs, etc.
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 Consistently deploys to multiple environments with no changes to the process. Having reusable processes across environments from Dev to Production make deployments more consistent and easier to manage. IBM UrbanCode Deploy has an easy to understand UI, to be able to review if a deployment has successfully completed or not, and details if it did not work. Using the UI is simple and easy to understand. Scheduling and approvals are built-in as configured for the deployments. This allows us to use the same deployment process, but get approvals as needed when code is moved up to the upper environments. 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 IBM UrbanCode Deploy does code deployments easy enough, but configurations or ex deployments are a little more complicated. I work on packaged systems, so most of the code I get is form a vendor that I have to deploy. IBM UebanCode Deploy integration into the mainframe world would be ideal. My company uses Mainframe and OpenSystems technologies, and many times there are dependencies between the deployments. 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 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 I've not worked directly with IBM UrbanCode Deploy support. My DevOps team administers the environment and deals with that.
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 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 IBM UrbanCode Deploy has had a positive impact on making deployments much easier and quicker to do. Downtime for a system is greatly reduced and deployments go much smoother as the processes are complete repeatable and not manual. Read full review ScreenShots