diff options
| author | Isaac Hollander McCreery <ihmccreery@google.com> | 2016-05-16 07:29:04 -0700 |
|---|---|---|
| committer | Isaac Hollander McCreery <ihmccreery@google.com> | 2016-05-16 07:29:04 -0700 |
| commit | 9532507be58198e6d94c85e2dc44c690213370ae (patch) | |
| tree | afc4e7d7bb46999d46e9f2b7d1cae594e840a84c | |
| parent | b2bfe549a34be0ae48fb7360c9431b03201afc5d (diff) | |
Fix link to Jenkins
| -rw-r--r-- | releasing.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/releasing.md b/releasing.md index 0f08caf6..5747ed6b 100644 --- a/releasing.md +++ b/releasing.md @@ -82,11 +82,11 @@ from, and other prerequisites. * You should still look for green tests, (see below). No matter what you're cutting, you're going to want to look at -[Jenkins](http://go/k8s-test/). Figure out what branch you're cutting from, -(see above,) and look at the critical jobs building from that branch. First -glance through builds and look for nice solid rows of green builds, and then -check temporally with the other critical builds to make sure they're solid -around then as well. +[Jenkins](http://kubekins.dls.corp.google.com/) (Google internal only). Figure +out what branch you're cutting from, (see above,) and look at the critical jobs +building from that branch. First glance through builds and look for nice solid +rows of green builds, and then check temporally with the other critical builds +to make sure they're solid around then as well. If you're doing an alpha release or cutting a new release series, you can choose an arbitrary build. If you are doing an official release, you have to |