cert-manager/gcb/build_cert_manager.yaml
Richard Wall 25c7ffa5d9 Use a better supported machine type
N1_HIGHCPU_32 is no longer listed in the table of supported GCB machine types,
but there is the following foot note in the documentation:
> Cloud Build continues to offer n1-highcpu-8 and n1-highcpu-32 machine types. They are offered at the same price as e2-highcpu-8 and e2-highcpu-32

https://cloud.google.com/build/pricing

Signed-off-by: Richard Wall <richard.wall@venafi.com>
2024-09-26 11:44:32 +01:00

40 lines
1.5 KiB
YAML

# This cloudbuild config file is intended to be triggered when a tag is pushed to the cert-manager repo
# and will build a cert-manager release and push to Google Cloud Storage (GCS).
# The release won't be published automatically; this file just defines the build steps.
# The full release and publish process is documented here:
# https://cert-manager.io/docs/contributing/release-process/
timeout: 2700s # 45m
steps:
# cert-manager relies on the git checkout to determine release version, among other things
# By default, gcb only does a shallow clone, so we need to "unshallow" to get more details
- name: gcr.io/cloud-builders/git
args: ['fetch', '--unshallow']
## Build release artifacts and push to a bucket
- name: 'europe-west1-docker.pkg.dev/cert-manager-tests-trusted/cert-manager-infra-images/make-dind:20240422-6b43e85-bookworm'
entrypoint: bash
args:
- -c
- |
set -eu -o pipefail
make vendor-go
make CMREL_KEY="${_KMS_KEY}" RELEASE_TARGET_BUCKET="${_RELEASE_TARGET_BUCKET}" -j8 upload-release
echo "Wrote to ${_RELEASE_TARGET_BUCKET}"
tags:
- "cert-manager-tag-push"
- "ref-${REF_NAME}-${COMMIT_SHA}"
substitutions:
_KMS_KEY: "projects/cert-manager-release/locations/europe-west1/keyRings/cert-manager-release/cryptoKeys/cert-manager-release-signing-key/cryptoKeyVersions/1"
_RELEASE_TARGET_BUCKET: "cert-manager-release"
options:
# https://cloud.google.com/build/docs/optimize-builds/increase-vcpu-for-builds
# https://cloud.google.com/build/pricing
machineType: E2_HIGHCPU_32