node-feature-discovery/cloudbuild.yaml

timeout: 3000s
steps:
  - name: gcr.io/k8s-staging-test-infra/gcb-docker-gcloud:v20211118-2f2d816b90
    entrypoint: scripts/test-infra/push-image.sh
    env:
    - IMAGE_REGISTRY=gcr.io/$PROJECT_ID
    - _GIT_TAG=$_GIT_TAG
    - IMAGE_EXTRA_TAG_NAMES=$_PULL_BASE_REF
    - HOME=/root
substitutions:
  _GIT_TAG: '0.0.0'
  _PULL_BASE_REF: 'master'
options:
  substitution_option: ALLOW_LOOSE
  machineType: 'E2_HIGHCPU_8'
cloudbuild: increase the image build timeout Attempt to fix occasional (rare) build failures. 2024-07-09 09:35:33 +00:00			`timeout: 3000s`
Add cloudbuild.yaml Basic google cloud build configuration. 2020-08-07 16:15:32 +00:00			`steps:`
images: fix invalid k8s-staging-test-infra/gcb-docker-gcloud tag 2021-11-30 21:37:12 +00:00			`- name: gcr.io/k8s-staging-test-infra/gcb-docker-gcloud:v20211118-2f2d816b90`
cloudbuild.yaml: build using make Use make for building our container image (through a new push-image.sh script) instead of building directly with docker. This way we avoid the container image tag naming hassle where we build and push the image on "image-pushing" prow job and need to be able to reliably re-create the same tag on the "testing" side for end-to-end tests. This also has the advantage that the same mechanism (make) is used everywhere, i.e. in image-pushing, testing and locally. 2020-09-03 09:12:13 +00:00			`entrypoint: scripts/test-infra/push-image.sh`
			`env:`
cloudbuild.yaml: use staging container image repo Use the staging repository for tagging/pushing container images. We aren't able to (and wouldn't want to) push directly to the production repository that is the default in the Makefile. 2020-09-04 05:02:23 +00:00			`- IMAGE_REGISTRY=gcr.io/$PROJECT_ID`
cloudbuild.yaml: set _GIT_TAG in env Needed by push-image.sh. 2020-09-03 16:39:18 +00:00			`- _GIT_TAG=$_GIT_TAG`
cloudbuild.yaml: build using make Use make for building our container image (through a new push-image.sh script) instead of building directly with docker. This way we avoid the container image tag naming hassle where we build and push the image on "image-pushing" prow job and need to be able to reliably re-create the same tag on the "testing" side for end-to-end tests. This also has the advantage that the same mechanism (make) is used everywhere, i.e. in image-pushing, testing and locally. 2020-09-03 09:12:13 +00:00			`- IMAGE_EXTRA_TAG_NAMES=$_PULL_BASE_REF`
cloudbuild.yaml: set HOME to /root As per https://github.com/kubernetes/test-infra/blob/master/config/jobs/image-pushing/README.md we need that for buildx. 2022-01-20 17:06:06 +00:00			`- HOME=/root`
Add cloudbuild.yaml Basic google cloud build configuration. 2020-08-07 16:15:32 +00:00			`substitutions:`
			`_GIT_TAG: '0.0.0'`
			`_PULL_BASE_REF: 'master'`
			`options:`
			`substitution_option: ALLOW_LOOSE`
cloudbuild.yaml: downgrade machine type to e2-highcpu-8 The higher tier builder didn't give any advantage, especially after armv7 builds were disabled. Let's revert back to highcpu-8. 2024-04-26 15:39:18 +00:00			`machineType: 'E2_HIGHCPU_8'`