AWS CodeBuild

Dagger provides a programmable container engine that allows you to migrate most of your AWS CodeBuild specification into Dagger Functions. This allows you to execute your pipeline the same locally and in AWS CodeBuild, with the additional benefits of intelligent caching and portability.

How it works

When running a CI pipeline with Dagger using AWS CodeBuild, the general workflow looks like this:

1. AWS CodeBuild receives a trigger based on a repository event.
2. AWS CodeBuild begins processing the build instructions in the buildspec.yml file.
3. AWS CodeBuild downloads the Dagger CLI.
4. AWS CodeBuild executes one (or more) Dagger CLI commands, such as dagger call ....
5. The Dagger CLI attempts to find an existing Dagger Engine or spins up a new one inside the GitLab runner.
6. The Dagger CLI calls the specified Dagger Function and sends telemetry to Dagger Cloud if the DAGGER_CLOUD_TOKEN environment variable is set.
7. The AWS CodePipeline completes with success or failure. Logs appear in the AWS CodeBuild interface as usual.

Prerequisites

• An AWS CodeBuild project connected with a source code repository in GitLab, GitHub, BitBucket or any other supported provider

Example

The following example demonstrates how to call a Dagger Function in an AWS CodeBuild project.

The following is a more complex example demonstrating an AWS CodeBuild project that checks out source code, calls a Dagger Function to test the project, and then calls another Dagger Function to build and publish a container image of the project. This example uses a simple Go application and assumes that you have already forked it in the repository connected to the AWS CodeBuild project.

Resources

If you have any questions about additional ways to use AWS CodeBuild with Dagger, join our Discord and ask your questions in our AWS channel.

About AWS CodeBuild

AWS CodeBuild is a managed service to test, build and deploy applications in public or private repositories.