Comment on page
Google Cloud Build
Google's Cloud Build is a popular, hosted build platform with deep integrations into the Google Cloud ecosystem. It includes native support for containerized builds, as well as other build scenarios. This guide will cover the use of Earthly within the
cloudbuild.yaml spec (though it should be easily ported over to the json format if desired).Earthly itself is able to run as expected within Cloud Build, including privileged mode features like
WITH DOCKER. However, Application Default Credentials are not available, so any gcloud or gsutil commands within your Earthfile will require additional manual configuration via a service account.Depending on your needs and existing infrastructure, there may be additional configuration needed in your Google Cloud environment.
Ensure that your repositories are connected to Cloud Build. Google has a fantastic walkthrough for this.
Note
If you do not intend to use any Google Cloud utilities or capabilities within your build, this service account configuration is optional.
Begin by following Google's instructions to create a service account. These instructions are partially duplicated below, with some screenshots for completeness.
Start by creating a build service account. Go to the "Create service account" page in the "IAM & Admin" API section, choose the appropriate project, and fill out the step 1 "Service account details". When you are done, click "Create and Continue".
Step One of configuring a new Google Cloud Service account, with account name and description fields
The creation steps should now ask you for a role to use in your build. The needs for each build are different; so examine your needs, and take care to grant the least privilege needed for your build. One reasonable starting point might be the default Cloud Build service account permissions.
Step two of configuring a new Google Cloud Service account, with a chosen role selected
Click "Done". The console should navigate you to a list of service accounts within the project. At this point, the account should be created, but we still need to create an account key. To do this, click on the email address for this service account in the list.
The Google Cloud list view of service accounts, with our new account highlighted
Then select "Keys" from the top navigation.
The top nav of the service account drilldown, with the keys tab highlighted
Click "Add Key", and then "Create New Key". Choose "JSON" as the key format, and click create. This will download the key to your computer, and you should see it in the list of keys.
The list view of available keys for a Google Cloud service account
Stash the key in your secret management utility of choice. You'll need to make this key available to your build at runtime. For the rest of our example, we will be using Earthly's Cloud Secrets.
Often, external secrets management requires some kind of bootstrapping secret (or additional integration) to allow you to access the rest of the secrets in your store. Earthly is no different. We will keep our
EARTHLY_TOKEN in Googles Secret Manager for ease of use.Note
It is also possible to perform these steps via the CLI; the steps are also detailed in Googles instructions. It can also be automated using much of the same steps.
earthly misinterprets the Cloud Build environment as a terminal. To hide the ANSI color codes, set NO_COLOR to 1.Note
This example is not production ready, and is intended to showcase configuration needed to get Earthly off the ground. If you run into any issues, or need help, don't hesitate to reach out!
Start by adding a new Trigger. Triggers are the things that link changes in your source code with new instances of builds in Cloud Build. Start by clicking on "Create Trigger".
The triggers page for a project, with "Create Trigger" highlighted.
Fill out the "Name", "Description", and "Event" sections for this trigger, as they make sense for your project. For our example (and for ease of testing) we will be using the "Manual Invocation" trigger here.
Creating a trigger for Google Cloud Build, specifying a name, description, and trigger event
Configure your source repository. If you do not see your desired repository in the drop down list, follow Google's instructions to add it.
Creating a trigger for Google Cloud Build, specifying a repository and branch name
Finally, fill in the "Configuration" section. For Earthly, you can only use the "Cloud Build configuration file", as Earthly itself will also be running containers. Our example will also be using an embedded
cloudbuild.yaml.
Creating a trigger for Google Cloud Build, specifying the configuration, including cloudbuild location and configuration type
Click "Done" and you will be navigated back to the Triggers list view. To test the build, click "Run" since we chose a manual trigger only:
Google Cloud Build Trigger list, with the manual run button highlighted
Running this build will use the
cloudbuild.yaml file in our sample repository. This file is also a key part of the build, so lets break this down as well. - id: 'build'
name: 'earthly/earthly:v0.7.22'
args:
- --allow-privileged
- +docker
The second step runs a sample, Google Cloud Build only example to show how you would use an external service account to do things that normally requires credentials.
- id: 'gcp-test'
name: 'earthly/earthly:v0.7.22'
args:
- +gcp-cloudbuild
secretEnv:
- 'EARTHLY_TOKEN'
The secret environment variable bootstraps the Earthly secret store, and we can load it from Google's Secret Store like this:
availableSecrets:
secretManager:
- versionName: projects/earthly-jupyterlab/secrets/EARTHLY_TOKEN/versions/2
env: 'EARTHLY_TOKEN'
Last modified 10d ago