Amazon CodeBuild FAQs
Q: What is Amazon CodeBuild?
Amazon CodeBuild is a fully managed continuous integration service in the cloud. CodeBuild compiles source code, runs tests, and produces packages that are ready to deploy. CodeBuild eliminates the need to provision, manage, and scale your own build servers. CodeBuild automatically scales up and down and processes multiple builds concurrently, so your builds don’t have to wait in a queue. You can get started quickly by using CodeBuild prepackaged build environments, or you can use custom build environments to use your own build tools. With CodeBuild, you only pay by the minute.
Q: Why should I use CodeBuild?
Instead of having to set up, patch, and maintain the build server software yourself, you can use CodeBuild’s fully managed experience. You submit your build jobs to CodeBuild, and it runs them in temporary compute containers that are created fresh on every build and then discarded when finished. You don’t need to manage build server hardware or software. CodeBuild also automatically scales to meet your build volume. It immediately processes each build you submit and can run separate builds concurrently, meaning your builds are never left waiting in a queue.
Q: What is the pricing for CodeBuild?
See the Amazon CodeBuild pricing page for details.
Q: What is a build project?
A build project is used to define how CodeBuild will run a build. It includes information such as where to get the source code, which build environment to use, the build commands to run, and where to store the build output. A build environment is the combination of operating system, programming language runtime, and tools used by CodeBuild to run a build.
Q: How do I configure a build project?
A build project can be configured through the console or the Amazon CLI. You specify the source repository location, the runtime environment, the build commands, the IAM role assumed by the container, and the compute class required to run the build. Optionally, you can specify build commands in a buildspec.yml file.
Q: Which source repositories does CodeBuild support?
CodeBuild can connect to Amazon S3, GitHub, GitHub Enterprise and Bitbucket to pull source code for builds.
Q: Which programming frameworks does CodeBuild support?
CodeBuild provides preconfigured environments for supported versions of Java, Ruby, Python, Go, Node.js, Android, .NET Core, PHP, and Docker. You can also customize your own environment by creating a Docker image and uploading it to the Amazon EC2 Container Registry or the Docker Hub registry. You can then reference this custom image in your build project.
Q: Which preconfigured Windows build runtimes does CodeBuild provide?
CodeBuild provides a preconfigured Windows build environment for .NET Core 2.0. We would like to provide a preconfigured build environment for Microsoft .NET Framework customers, many of whom already have a license to use the Microsoft proprietary libraries. However, Microsoft has been unwilling to work with us in addressing these customer requests at this time. You can customize your environment yourself to support other build targets, such as .NET Framework, by creating a Docker image and uploading it to the Amazon EC2 Container Registry or the Docker Hub registry. You can then reference this custom image in your build project.
Q: What happens when a build is run?
CodeBuild will create a temporary compute container of the class defined in the build project, load it with the specified runtime environment, download the source code, execute the commands configured in the project, upload the generated artifact to an Amazon S3 bucket, and then destroy the compute container. During the build, CodeBuild will stream the build output to the service console and also Amazon CloudWatch
Q: How do I set up my first build?
Sign in to the Amazon Web Services Management Console, create a build project, and then run a build. You can also use CodeBuild Local to test and debug your build locally.
Q: Can I use CodeBuild with Jenkins?
Yes. The CodeBuild Plugin for Jenkins can be used to integrate CodeBuild into Jenkins jobs. The build jobs are sent to CodeBuild, eliminating the need for provisioning and managing the Jenkins worker nodes.
Q: How can I view past build results?
You can access your past build results through the console, CloudWatch or the API. The results include outcome (success or failure), build duration, output artifact location, and log location. With the CodeBuild dashboard, you can view metrics to understand build behavior over time. The dashboard displays number of builds attempted, succeeded, and failed, as well as build duration. You can also visit the CloudWatch console to view more detailed build metrics. To learn more about monitoring CodeBuild with CloudWatch, visit our documentation.
Q: How can I debug a past build failure?
You can debug a build by inspecting the detailed logs generated during the build run or you can use CodeBuild Local to locally test and debug your builds.
Q: Why is build.general1.small not supported for .NET Core for Windows build environments?
The .NET Core for Windows build environment requires more memory and processing power than is available in the build.general1.small compute instance type due to the size of the Windows Docker base container and additional libraries. Due to this limitation, there is no free tier for the .NET Core for Windows build environment.
Q: How does CodeBuild isolate builds that belong to other customers?
CodeBuild runs your build in fresh environments isolated from other users and discards each build environment upon completion. CodeBuild provides security and separation at the infrastructure and execution levels.
Q: Can I use Amazon Identity and Access Management (IAM) to manage access to CodeBuild?
Yes. You can control access to your build projects through resource-level permissions in IAM policies.
Q: Which regions does CodeBuild support?
See Regional Products and Services for details.
Learn more about Amazon CodeBuild pricing