github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix link to Jenkins

pull/6/head
Isaac Hollander McCreery 2016-05-16 07:29:04 -07:00
parent a0cc59f28a
commit 4ef33834d3
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/devel/releasing.md
View File

@ -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