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.
The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
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.
We are creating pipelines with the help of the solution. We need to do some testing and deployments over our web server. We create a new bucket in which we create a CI/CD pipeline and put our deployments into it. CodeBuild deploys it through GitHub on the target server.
If we face any issues, we can find out where the issue is. We can check it on the script. We can easily do debugging or troubleshooting. We had development projects. We are using CodeBuild for five to ten applications. We deploy them first in the development environment. After the Sanity tests and the UAT, we deploy them on the production environment. The integration with other AWS services has streamlined our workflow. It is similar to any other product. We must define the roles. It is easy to give permission to other services.
The deployment fails sometimes. We need to reset the pipeline to do the deployment.
I have been using the solution for the past four years.
I rate the tool’s stability an eight out of ten. Some applications must be checked end-to-end because Java does not work sometimes, and we do everything manually and restart. We must check whether all parameters are correct on the scripting side and whether there are any dependencies we must know about.
We can create multiple pipelines. If we need multiple deployments for multiple projects, we create multiple pipelines to do the deployment. We have 50 to 80 users.
The support is good.
Positive
The initial setup was difficult the first time since we had to configure it end-to-end. We got some errors. After the configuration, we did not face any major roadblocks. The deployment took five to ten minutes.
Apart from Jenkins, I love to use CodeBuild.
I will recommend the tool to others. We must know the dependencies in our projects, the services we need to deploy, and the different things needed in the scripts. We must do the IAM configurations on AWS before initializing the pipeline. Overall, I rate the products nine out of ten.
