Publish nightly knative/build-pipeline releases to knative-nightly

hack/README.md

@@ -0,0 +1,8 @@
+# Assorted scripts for development
+
+This directory contains several scripts useful in the development process of Knative Build Pipeline.
+
+* `release.sh` Creates a new [release](release.md) of Knative Build Pipeline.
+* `update-codegen.sh` Updates auto-generated client libraries.
+* `update-deps.sh` Updates Go dependencies.
+* `verify-codegen.sh` Verifies that auto-generated client libraries are up-to-date.

hack/release.md

@@ -0,0 +1,72 @@
+# Creating a new Knative Build Pipeline release
+
+The `release.sh` script automates the creation of Knative Build Pipeline
+releases, either nightly or versioned ones.
+
+By default, the script creates a nightly release but does not publish anywhere.
+
+## Common flags for cutting releases
+
+The following flags affect the behavior of the script, no matter the type of
+the release.
+
+* `--skip-tests` Do not run tests before building the release. Otherwise,
+build, unit and end-to-end tests are run and they all must pass for the
+release to be built.
+* `--tag-release`, `--notag-release` Tag (or not) the generated images
+with either `vYYYYMMDD-<commit_short_hash>` (for nightly releases) or
+`vX.Y.Z` for versioned releases. *For versioned releases, a tag is always
+added.*
+* `--publish`, `--nopublish` Whether the generated images should be published
+to a GCR, and the generated manifests written to a GCS bucket or not. If yes,
+the destination GCR is defined by the environment variable
+`$BUILD_PIPELINE_RELEASE_GCR` (defaults to `gcr.io/knative-nightly`) and the
+destination GCS bucket is defined by the environment variable
+`$BUILD_PIPELINE_RELEASE_GCS` (defaults to `knative-nightly/build-pipeline`).
+If no, the images will be pushed to the `ko.local` registry, and the manifests
+written to the local disk only (in the repository root directory).
+
+## Creating nightly releases
+
+Nightly releases are built against the current git tree. The behavior of the
+script is defined by the common flags. You must have write access to the GCR
+and GCS bucket the release will be pushed to, unless `--nopublish` is used.
+
+Examples:
+
+```bash
+# Create and publish a nightly, tagged release.
+./hack/release.sh --publish --tag-release
+
+# Create release, but don't test, publish or tag it.
+./hack/release.sh --skip-tests --nopublish --notag-release
+```
+
+## Creating versioned releases
+
+*Note: only Knative admins can create versioned releases.*
+
+To specify a versioned release to be cut, you must use the `--version` flag.
+Versioned releases are usually built against a branch in the Knative Build
+Pipeline repository, specified by the `--branch` flag. 
+
+* `--version` Defines the version of the release, and must be in the form
+`X.Y.Z`, where X, Y and Z are numbers.
+* `--branch` Defines the branch in Knative Build Pipeline repository from which
+the release will be built. If not passed, the `master` branch at HEAD will be
+used. This branch must be created before the script is executed, and must be
+in the form `release-X.Y`, where X and Y must match the numbers used in the
+version passed in the `--version` flag. This flag has no effect unless
+`--version` is also passed.
+* `--release-notes` Points to a markdown file containing a description of the
+release. This is optional but highly recommended. It has no effect unless
+`--version` is also passed.
+
+If this is the first time you're cutting a versioned release, you'll be prompted
+for your GitHub username, password, and possibly 2-factor authentication
+challenge before the release is published.
+
+The release will be published in the *Releases* page of the Knative Build
+Pipeline repository, with the title *Knative Build Pipeline release vX.Y.Z* and
+the given release notes. It will also be tagged *vX.Y.Z* (both on GitHub and as
+a git annotated tag).

hack/release.sh

@@ -17,8 +17,8 @@
 source $(dirname $0)/../vendor/github.com/knative/test-infra/scripts/release.sh
 
 # Set default GCS/GCR
-: ${BUILD_PIPELINE_RELEASE_GCS:="knative-releases/build-pipeline"}
-: ${BUILD_PIPELINE_RELEASE_GCR:="gcr.io/knative-releases"}
+: ${BUILD_PIPELINE_RELEASE_GCS:="knative-nightly/build-pipeline"}
+: ${BUILD_PIPELINE_RELEASE_GCR:="gcr.io/knative-nightly"}
 readonly BUILD_PIPELINE_RELEASE_GCS
 readonly BUILD_PIPELINE_RELEASE_GCR