AWS CodeBuild Reviews

I utilize CodeBuild's broad services.

The integration with other AWS services is important as well. These features make CodeBuild valuable to me.

I faced some challenges while using CodeBuild. I would like to see some improvements in certain limitations of the product.

I have used CodeBuild for some time.

There have been times when CodeBuild has shown some instability, like bugs or breakdowns.

The initial setup of CodeBuild is easy.

Regarding the pricing of CodeBuild, I cannot speak to the exact price. 

I recommend it to others. From one to ten, I would rate CodeBuild eight out of ten.

Our main use case for AWS CodeBuild is building our microservice-based application in the IT industry.

The tool is used to build and test code. I find its biggest advantages are elasticity and reliability. We can easily assign as many computing resources as needed to build our code, which is much simpler than traditional methods that require server upgrades. It's a serverless tool, so it's very flexible and elastic.

Integration with other AWS services and third-party tools like GitLab or Jenkins is simple. I haven't faced any challenges using AWS CodeBuild. It's straightforward and communicates well with CodeCommit for code storage, or it can fetch code from GitHub.

For improvement, I'd suggest more build instance-type options. There's a big jump from 15 gigabytes of RAM to 150, and I'd like something in between as the larger option is too expensive for our needs.

I have been working with the product for four years. 

The solution is highly stable; I rate it a ten out of ten. 

The tool is very scalable, and I rate it a ten out of ten. More than 30 developers on our team indirectly use AWS CodeBuild in our development process. Developers push their code to CodeCommit, which goes through the CodeBuild pipeline.

We're very satisfied with AWS support. We're on the Enterprise plan, which I'd rate ten out of ten for support quality.

Positive

Setting the tool up is relatively easy—I'd rate it eight out of ten—but some AWS knowledge is required.

AWS CodeBuild is part of a full CICD suite in AWS, working alongside CodeCommit, CodeDeploy, and CodePipeline. It's a cloud solution where CodeCommit stores the code, AWS CodeBuild builds it, CodeDeploy deploys it, and CodePipeline configures all these steps as needed.

The tool saves us money as it's on-demand, only working when triggered.

AWS CodeBuild is free. We only pay for our code's compute resources during the build process. For example, if our code takes ten minutes to build, we only pay for those ten minutes of computing time. CodeDeploy and CodePipeline are free because they're serverless and don't require computing resources. CodeCommit has minimal costs for storing code.

If you run AWS applications, I advise those considering AWS CodeBuild to use the entire CodePipeline Suite (CodeCommit, AWS CodeBuild, and CodeDeploy). It's a great CICD tool compared to third-party options. I've used GitLab and Jenkins before, and while they're good, I prefer AWS solutions because they're reliable and fully managed, offering the best SLA in the market.

I always recommend going with native tools when possible. Overall, I'd rate AWS CodeBuild ten out of ten.

It's a pipeline component. So if you can use CodeBuild, you can build up a pipeline. 

The integration is a good feature. 

They can further improve the integration of the Bitbucket for CodeBuild. 

I have been using AWS CodeBuild for two years. 

It is a very stable solution. 

Twelve people are using the solution at present. 

We pay a monthly licensing fee. 

Overall, I rate the solution a ten out of ten. 

In our environment, the primary use case for AWS CodeBuild is to build Docker images for containerized applications. We also use it to build application binaries. 

One of the most valuable features of AWS CodeBuild is its variable feature. Instead of having to rewrite credentials or configurations multiple times for different stages, we can define these variables once and use them across various steps in the build pipeline. With a clear characterization of steps and instructions, we better understand what actions are being taken within each pipeline stage.

While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected. Although conditions were functioning correctly, the lack of support for looping hindered my ability to execute certain tasks efficiently.

We have been using AWS CodeBuild for more than 2 years.

We haven't encountered any stability issues with CodeBuild. It has worked perfectly for you without any downtimes, which is essential, especially in modern environments where containerized applications are prevalent.

The platform's scalability of CodeBuild varies from client to client requirements.

We have yet to contact the technical support team, but the services are stable.

The initial setup for CodeBuild is straightforward. There is no need for installation. You just have to log in to your account and start writing scripts to build your application.

Using AWS CodeBuild might involve some initial expenses, but there are strategies to optimize costs and ensure a return on investment. Leveraging features like caching files and using the artifact feature to pass packages between stages can help reduce costs by minimizing the need to fetch files repeatedly.

Despite the cost, it is worth the investment.

CodeBuild integrates with other AWS services, enhancing the build environment's functionality. For instance, it works seamlessly with AWS Elastic Container Registry (ECR). It allows you to build and deploy container images to ECR directly from CodeBuild.

It is easy for someone with experience in shell scripting or writing code to learn. Once familiar with these skills, using CodeBuild becomes quite straightforward.

Following the predefined stages organizes the steps effectively. This helps users build their architecture with ease.

I rate it an eight out of ten.