AWS CodeBuild vs. Google Cloud Build

I enjoy it - very cool service. I would say give it a try.

Incentivized

• Customization
• Do code builds within a schedule or when the source code changes
• Only pay for the build time used

Incentivized

• It was difficult to create a branching strategy with GitHub. We had everything running from main, but in a true devops environment, we would like to incorporate a true branching strategy.
• I would like to share build projects with each AWS account we utilize versus creating a build project in each account. It will allow us consistent deployments across the board.
• The error logs are natively in AWS, but when developers do not have access, there is no way for them to view error logs for maintenance other than an admin who has access to share the error logs.

Incentivized

It is a highly usable, well integrated CI/CD service, patricularly for AWS-centric organizations. It is a strong balance between simplicity and flexibility. Security was integrated with AWS Secrets Manager allowing secrets to be retrieved dynamically - a huge usability win for us. I did not enjoy the manual build for each environment

Incentivized

AWS CodeBuild provides the option to fully implement the build in the cloud without wasting your local resources (computer and network) providing independence to developers to invest those resources in other processes. It also provides a robust platform with a lot of customizations or just a script for each language.

Incentivized

• It has a positive ROI

Incentivized