node-feature-discovery/scripts/test-infra/push-image.sh

#!/bin/bash -e

# Override VERSION if _GIT_TAG is specified. Strip 10 first characters
# ('vYYYYMMDD-') from _GIT_TAG in order to get a reproducible version and
# container image tag
VERSION_OVERRIDE=${_GIT_TAG+VERSION=${_GIT_TAG:10}}

make image $VERSION_OVERRIDE
make push $VERSION_OVERRIDE
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 12:12:13 +03:00			`#!/bin/bash -e`

scripts: explicitly override VERSION in push-image.sh Without using -e to override variables from the environment. 2020-09-15 11:46:48 +03:00			`# Override VERSION if _GIT_TAG is specified. Strip 10 first characters`
			`# ('vYYYYMMDD-') from _GIT_TAG in order to get a reproducible version and`
			`# container image tag`
			`VERSION_OVERRIDE=${_GIT_TAG+VERSION=${_GIT_TAG:10}}`
scripts: use a reproducible version in push-image.sh We don't have a full git repo in the gcb builds so our version/tag magic inside the makefile does not work. With this patch we get the version information from the builder environment - fortunately we can do that by simply stripping the date prefix from the _GIT_TAG variable. By stripping the date of we match what our makefile does. 2020-09-03 17:00:10 +03:00
scripts: explicitly override VERSION in push-image.sh Without using -e to override variables from the environment. 2020-09-15 11:46:48 +03:00			`make image $VERSION_OVERRIDE`
			`make push $VERSION_OVERRIDE`