Add Container Image Build Automation

The cloudbuild.yaml file will be used by the prow job to automate the
container build and push tasks. This is a prerequisite to setting up the
prow job.

cloudbuild.yaml

@@ -0,0 +1,24 @@
+# See https://cloud.google.com/cloud-build/docs/build-config
+
+# this must be specified in seconds. If omitted, defaults to 600s (10 mins)
+timeout: 1200s
+# this prevents errors if you don't use both _GIT_TAG and _PULL_BASE_REF,
+# or any new substitutions added in the future.
+options:
+ substitution_option: ALLOW_LOOSE
+steps:
+ - name: 'gcr.io/k8s-testimages/gcb-docker-gcloud:v20190906-745fed4'
+ entrypoint: make
+ env:
+ - DOCKER_CLI_EXPERIMENTAL=enabled
+ - VERSION=$_GIT_TAG
+ - BASE_REF=$_PULL_BASE_REF
+ args:
+ - push-release-image
+substitutions:
+ # _GIT_TAG will be filled with a git-based tag for the image, of the form vYYYYMMDD-hash, and
+ # can be used as a substitution
+ _GIT_TAG: '12345'
+ # _PULL_BASE_REF will contain the ref that was pushed to to trigger this build -
+ # a branch like 'master' or 'release-0.2', or a tag like 'v0.2'.
+ _PULL_BASE_REF: 'master'

doc/release-guide.md

@@ -2,7 +2,14 @@
 
 ## Semi-automatic
 
-TODO - update after container image build prow job is created.
+1. Make sure your repo is clean by git's standards
+2. Create a release branch `git checkout -b release-1.19` (not required for patch releases)
+3. Push the release branch to the scheduler-plugins repo and ensure branch protection is enabled (not required for patch releases)
+4. Tag the repository from the `master` branch (from the `release-1.19` branch for a patch release) and push the tag `VERSION=v0.19.0 git tag -m $VERSION $VERSION; git push origin $VERSION`
+5. Publish a draft release using the tag you just created
+6. Perform the [image promotion process](https://github.com/kubernetes/k8s.io/tree/master/k8s.gcr.io#image-promoter)
+7. Publish release
+8. Email `[email protected]` to announce the release
 
 ## Manual