Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds.
Cloud System Specialist at a financial services firm with 51-200 employees
Real User
Top 5
2024-08-20T07:32:18Z
Aug 20, 2024
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.
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.
The product must provide more integrations. It is a replica of Jenkins. We have a management overhead. When I build artifacts stored outside the S3 bucket, it will have additional charges on the storage volumes. If we use S3 buckets regularly, it is fine. However, when we store somewhere else, it will be an issue. There is no persistent storage or preservation of workspace between the builds. We must fix the dependencies every time, even if the dependencies are the same. It is unnecessary.
Build automation tools automate the time-consuming tasks inherent in creating a “build,” or usable version of an application. They automate and orchestrate the sometimes complex processes of compiling computer source code into binary code and packaging that binary code as well as running automated tests
Some PeerSpot members use build automation solutions. In reviews, they offer opinions on the most significant selection factors to consider when looking at this type of software. One theme...
Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds.
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.
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.
They can further improve the integration of the Bitbucket for CodeBuild.
The product must provide more integrations. It is a replica of Jenkins. We have a management overhead. When I build artifacts stored outside the S3 bucket, it will have additional charges on the storage volumes. If we use S3 buckets regularly, it is fine. However, when we store somewhere else, it will be an issue. There is no persistent storage or preservation of workspace between the builds. We must fix the dependencies every time, even if the dependencies are the same. It is unnecessary.