The cost structure is affordable for most builds except macOS servers. Standard builds can utilize AWS EC2 servers for background operations. However, macOS or iOS builds require physical servers maintained by Amazon. Triggering these builds essentially reserves the server for 24 hours, resulting in higher costs compared to readily available servers. Reserving a physical macOS server such as a Mac mini incurs substantially higher costs than standard server options.
AWS Devops Support Engineer at a recruiting/HR firm with 11-50 employees
Real User
Top 10
Apr 28, 2025
Issues with pricing have been mentioned, especially for new clients who might not realize the cost implications initially, such as leaving servers on for too long and incurring unexpectedly high bills without clear pricing visibility.
CodeBuild doesn't have a price for itself; it is included in a bundle with different services. I would rate the cost of this bundle, where CodeBuild is included, as five. It's rather affordable.
Cloud System Specialist at a financial services firm with 51-200 employees
Real User
Top 5
Aug 20, 2024
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.
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.
The pricing is okay. Jenkins is not costly, but we must pay for the underlying infrastructure. The infrastructure is continuously there for the entire duration. In AWS CodeBuild, we don't have a dedicated infrastructure. However, it works. The bill is almost the same. We can configure better instances if we need it to be faster.
AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers. CodeBuild scales continuously and processes multiple builds concurrently, so your builds are not left waiting in a queue. You can get started quickly by using prepackaged build environments, or you can create custom build environments that use your...
The cost structure is affordable for most builds except macOS servers. Standard builds can utilize AWS EC2 servers for background operations. However, macOS or iOS builds require physical servers maintained by Amazon. Triggering these builds essentially reserves the server for 24 hours, resulting in higher costs compared to readily available servers. Reserving a physical macOS server such as a Mac mini incurs substantially higher costs than standard server options.
Issues with pricing have been mentioned, especially for new clients who might not realize the cost implications initially, such as leaving servers on for too long and incurring unexpectedly high bills without clear pricing visibility.
Regarding pricing, AWS services are quite expensive compared to open source tools like Git that are available for free.
Regarding the pricing of CodeBuild, I cannot speak to the exact price.
CodeBuild doesn't have a price for itself; it is included in a bundle with different services. I would rate the cost of this bundle, where CodeBuild is included, as five. It's rather affordable.
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.
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.
We pay a monthly licensing fee.
The pricing is okay. Jenkins is not costly, but we must pay for the underlying infrastructure. The infrastructure is continuously there for the entire duration. In AWS CodeBuild, we don't have a dedicated infrastructure. However, it works. The bill is almost the same. We can configure better instances if we need it to be faster.