AWS CodeBuild vs. Azure Pipelines

If you have a set of AWS services deployed or looking to deploy a new application on AWS, then using amazon CodeBuild and other developer tools would be a good solution to get everything stayed within the Amazon network and improve both security and speed to market. However if you already have solution in cross platform, other solution might be better.

Incentivized

With a fully Microsoft Azure based workflow - Azure Pipelines makes absolute sense. Azure Pipelines are robust and work very well with SonarQube for test coverage and are shared with our developers. This prevents the developers for pushing code without unit tests across our backend and frontend platforms. We have reduced our instances of manual regression tests especially when there are multiple teams working across the same repositories.

Incentivized

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

Incentivized

• all in one place
• good ability to personalize deployment process
• easy to develop

Incentivized

• Not open source
• Not as rich in feature as competitors
• Less uiux friendly

Incentivized

• Error messaging when team members don't have permissions

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

The tools are very similar - but Azure Pipelines work best for Azure-based products are better suited for the stack. For our engineers, we could switch between all the various continuous integration/deployment tools without much issues, but it makes sense to use the stack recommended by Azure. Our team has the relevant support licences to get support from Microsoft for all our products.

Incentivized

• Return of investment
• Fast to market
• Lower cost

Incentivized

• We don't have to deploy changes manually
• But because of this that we automated some tasks, we need to be still aware of some edge cases we can meet and which can cause a pipelines failures
• We can deploy changes pretty fast

Incentivized