Publish nightly knative/eventing releases to knative-nightly (#651)

Part of knative/serving#2555.

hack/release.md

@@ -20,9 +20,9 @@ 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
-`$EVENTING_RELEASE_GCR` (defaults to `gcr.io/knative-releases`) and
+`$EVENTING_RELEASE_GCR` (defaults to `gcr.io/knative-nightly`) and
 the destination GCS bucket is defined by the environment variable
-`$EVENTING_RELEASE_GCS` (defaults to `knative-releases/eventing`). If no, the
+`$EVENTING_RELEASE_GCS` (defaults to `knative-nightly/eventing`). 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).
 

hack/release.sh

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

test/e2e-tests.sh

@@ -27,7 +27,7 @@
 
 source $(dirname $0)/../vendor/github.com/knative/test-infra/scripts/e2e-tests.sh
 
-readonly KNATIVE_EVENTING_SOURCES_RELEASE=https://knative-releases.storage.googleapis.com/eventing-sources/latest/release.yaml
+readonly KNATIVE_EVENTING_SOURCES_RELEASE=https://knative-nightly.storage.googleapis.com/eventing-sources/latest/release.yaml
 
 # Names of the Resources used in the tests.
 readonly E2E_TEST_NAMESPACE=e2etest