Skip to content

Commit fd47dc0

Browse files
committed
Use commit sha for version and add some docs about
secrets used in the cloudbuild config file
1 parent 5d4a602 commit fd47dc0

File tree

2 files changed

+7
-1
lines changed

2 files changed

+7
-1
lines changed

cloudbuild.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ options:
4040
dynamicSubstitutions: true
4141
substitutions:
4242
_NODE_VERSION: 16.16.0
43-
_VERSION: '{"version":"${BRANCH_NAME}_dev","commit":"${SHORT_SHA}","source":"https://github.com/taskcluster/taskcluster","build":"${BUILD_ID}"}'
43+
_VERSION: '{"version":"${BRANCH_NAME}_${SHORT_SHA}","commit":"${SHORT_SHA}","source":"https://github.com/taskcluster/taskcluster","build":"${BUILD_ID}"}'
4444
_IMAGE_NAME: gcr.io/${PROJECT_ID}/${PROJECT_ID}/${BRANCH_NAME}
4545
_IMAGE_VERSION: latest
4646
availableSecrets:

dev-docs/dev-deployment.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -353,3 +353,9 @@ Warning: by using this approach, you are responsible for maintenance and backups
353353
Once users are set, you can run `yarn dev:db:upgrade` (with running port-forward) to create db schema and stored functions
354354

355355
Now it should be possible to use postgres for dev purposes inside the cluster. Make sure to make backups.
356+
357+
## GCP Cloud Build
358+
359+
Commits that land on `main` trigger a build on GCP Cloud Build. This build is configured by the [`cloudbuild.yaml` file](../cloudbuild.yaml). Here's a link to Google's docs on the build config file schema for cloud build: https://cloud.google.com/build/docs/build-config-file-schema.
360+
361+
A couple secrets are used in the config and they are both stored in GCP Secret Manager. Follow [these docs](https://cloud.google.com/build/docs/securing-builds/use-secrets) to create more secrets or edit the current secrets. A new version needs to be created each time you change the secrets. The current cloudbuild config points to the latest version of the secrets, so any edits to these secrets will be automatically picked up.

0 commit comments

Comments
 (0)