From 4ef33834d3e0edafa6e7ff9870a125ed86bdf271 Mon Sep 17 00:00:00 2001 From: Isaac Hollander McCreery Date: Mon, 16 May 2016 07:29:04 -0700 Subject: [PATCH] Fix link to Jenkins --- docs/devel/releasing.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/devel/releasing.md b/docs/devel/releasing.md index 0f08caf6e04..5747ed6b368 100644 --- a/docs/devel/releasing.md +++ b/docs/devel/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