Reviews (1-7 of 7)
January 16, 2020
AWS CodePipeline is one piece of several autoscaling back-end infrastructures I have launched in AWS. CodePipeline, in conjunction with CodeDeploy, allows for automated testing, building & deployment of Github & S3 hosted code. CodePipeline can be thought of the orchestrator of a typical AWS code deployment setup. It allows you to setup the source of the code change (S3/Github/etc) and then define the steps the code takes. For example, you can implement a build step using AWS CodeBuild. You can also implement test & deploy steps. By using CodeDeploy, you can keep a fleet of instances up-to-date with the latest code releases.
- CodePipeline reacts very quickly to new GitHub commits. It often starts new builds nearly instantly after code is pushed.
- The CodePipeline console & wizard is very intuitive. It was very easy to setup CodePipeline instances and define exactly required stages & the services to fulfill the stages.
- CodePipeline allows you to easily restart failed steps, right from the status page. The web console shows the current status of the builds and seems to not lag too far behind the actual status.
- If you are not using GitHub, the setup for integrating with a repository is complicated. Doesn't appear to offer support for other revision control services or other revision control tools out-of-the-box.
- CodePipeline is probably too expensive for personal projects, especially if you use the other AWS tools for the pipeline steps like CodeDeploy.
- Not as flexible or customizable as a self-hosted Jenkins server.
Read Alec Dibble's full review
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.
February 15, 2020
AWS CodePipeline is used to manage CI/CD pipelines for various products we build for customers on AWS. It is being used for such products associated with various projects across our whole organization. It enabled us to build delivery pipelines for applications we are deploying on AWS native stacks.
- Running and managing deployments for AWS native applcations
- Seamlessly integrating the suite of build tools AWS has to offer
- Integration with build and version control services that are not native to AWS
Read Ramindu Deshapriya's full review
AWS CodePipeline is the best solution to use if your application stack is completely AWS-native. This means you are exclusively using AWS tools to manage your source control, build management, and you are deploying your applications to AWS services such as EC2, Elastic Beanstalk, Lambda, EMR, etc. It integrates very well with AWS CodeCommit, CodeBuild, and Elastic Beanstalk to manage source control, building, and deployment. However, it does not integrate too well with third-party source control and build management tools such as Github, Travis, Jenkins, Codeship, etc.
AWS CodePipeline was used as a CI/CD solution within AWS, specifically for instances where specific AWS IAM roles were needed. The DevOps department was the primary user, pushing out to development and other organizations. It was a comprehensive CI/CD solution that provided out-of-the-box performance and features, specifically around AWS deployments.
- Tight AWS integrations for AWS organization.
- Similar feature sets to other CI/CD solutions.
- Infrastructure as code (IAC) integration.
- Slightly inconsistent performance (has issues downloading public Docker Registry images).
- Minimal support.
- Complex initial setup.
Read Stephen Groat's full review
AWS CodePipeline is great for organizations that are bought into AWS and infrastructure as code (IaC) practices. Sharing of IaC modules through tools like the Terraform Registry will hopefully bring more open source CI/CD pipelines into the mix and create a strong DevOps community around CodePipeline. Until then, it will probably remain an expert product with minimal support.
August 06, 2019
Score 7 out of 10
AWS CodePipeline is being used as a continuous integration/continuous deployment tool at my organization. It is used by specific teams that require builds within a CI/CD developer workflow. The business problems it addresses is the need for automated code deployment and testing pipeline that allows for a continuous flow of code from testing to staging to deployment.
Read this authenticated review
AWS CodePipeline is well suited for a specific software engineering workflow. If there is a need to deploy code within a framework, then this is a great tool to automate the code deployments outward. The scenarios where it is less appropriate is in situations of internal tooling or other code that might not change as often or are tools running locally.
May 15, 2019
Score 9 out of 10
This tool is used by the entire software development department. It helps us to speed up the software development cycle. It helps us find errors quickly, make tests, deliver updates, and automate the launching process, compilation, integration, etc. It is a very versatile tool that helps improve productivity. It is excellent for agile development since it can be integrated with other tools and automate the entire software delivery process.
Read Winston Mendes's full review
AWS CodePipeline is excellent for software companies that need to make constant changes or updates in their projects. It is ideal for those that use agile development. It is also very good for startup companies that need to speed up the whole process of delivering their software. However, for those companies that make weekly, monthly, etc. deliveries, it is not the ideal tool. It is more for companies that make multiple daily deliveries.
CodePipeline is a very flexible continuous integration and continuous delivery tool. Our organization development team uses it to build and deploy our app; it makes deploying within the AWS environment a bit easier.
Read Richard Rout's full review
If you're already on AWS, then using it as your build/test/deploy system makes a lot of sense. However, there are easier tools out there to do it that may not be as flexible, or may work better with your source control system.
June 19, 2019
Score 9 out of 10
Our business uses AWS CodePipeline to connect our repository to our Snowflake Database. We are currently using it to push changes made in our repo to the Snowflake Database. It is a crucial part of our ingestion process and how we determine changes are made and when they are made. It addresses the need to make scheduled changes to our environment.
- It is reliable and works without errors
- It integrates well with our repository and all other AWS functions as well as our end database
- AWS CodePipeline is a very simple and straight forward tool, it does not add anything complex or make pushing changes easier.
Read this authenticated review
AWS CodePipeline is well suited if your company is already using AWS as the main tool. It also works with ATOM Repository and Snowflake cohesively. There are other options on the marketplace that have the same functionality as AWS CodePipeline. It is only really appropriate if its integrated in the rest of your AWS infrastructure.
AWS CodePipeline Scorecard Summary
About AWS CodePipeline
Amazon Web Services offers AWS CodePipeline supports a technology infrastructure with configuration and updating by providing continuous integration and delivery to automate the build, test, and release process.
Categories: Configuration Management
AWS CodePipeline Technical Details