Overall Satisfaction with AWS CodeDeploy
We use AWS CodeDeploy to manage our deployment pipeline. Several squads often have competing branches for features that need to be deployed into various environments for code checks and testing. AWS CodeDeploy gives us a tool to ensure that we do not deploy over one another and makes it clear to our QA/UAT teams when and where features are available so we can test them expediently.
- Simplifies checking the status of code branches
- Streamlines the deployment process
- Integrates into our Slack workflow for reserving environments
- When deploying a branch, sometimes the repository won't auto-populate, and you have to add the source manually
- Branching code deployments
- Environment management
- Status and progress indicators on code pipeline
- AWS CodeDeploy has reduced the engineer involvement in deployments
- Our QA team has been able to effectively deploy tickets for testing, and our Release Managers can manage production deployments
- Progress indicators have given us a better baseline for deployment times, which is helpful for time-sensitive releases
Do you think AWS CodeDeploy delivers good value for the price?
Are you happy with AWS CodeDeploy's feature set?
Did AWS CodeDeploy live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of AWS CodeDeploy go as expected?
I wasn't involved with the implementation phase
Would you buy AWS CodeDeploy again?
AWS CodeDeploy is helpful for managing multiple code pipelines and deployments to multiple environments. I use it primarily with help from our QA team when we need to ensure that branches get merged into environments with certain feature sets so the code changes can be tested appropriately. Aside from a few obtuse steps involved with loading the repository, it is straightforward to use and gives clear progress indicators.