История

Filippo Valsorda fc76638eb1 cmd/releasebot: skip tests on the second release round The alternative was to key the cache by tree instead of by commit, which currently should be perfectly valid, but make.bash seems cheap enough to just rerun. Change-Id: I8de031a6b7ebfbcf4ba1f903bbb14ef1d98cbfe1 Reviewed-on: https://go-review.googlesource.com/c/154342 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>		2019-01-09 19:54:22 +00:00
..
README.md	cmd/releasebot: add support for beta releases	2018-06-19 19:43:43 +00:00
gcs.go	cmd/releasebot: adapt to new minor release process	2018-06-13 21:27:35 +00:00
git.go	cmd/releasebot: run all.bash in prepare mode	2019-01-09 19:52:41 +00:00
github.go	cmd/releasebot: add support for security releases	2018-12-12 22:06:52 +00:00
http.go	cmd/releasebot: initial release process automation	2017-11-13 15:36:14 +00:00
main.go	cmd/releasebot: skip tests on the second release round	2019-01-09 19:54:22 +00:00
markdown.go	cmd/releasebot: adapt to new minor release process	2018-06-13 21:27:35 +00:00

README.md

golang.org/x/build/cmd/releasebot

Command releasebot runs a Go release.

The release happens in two stages:

the prepare stage checks preconditions, and if needed makes the release commit and mails it for review;
the release stage runs after the release commit (if any) is merged, and it tags, builds and cleans up the release.

At the moment only minor and beta releases are supported.

Permissions

The user running a release will need:

A GitHub personal access token with the public_repo scope in ~/.github-issue-token, and an account with write access to golang/go
gomote access and a token in your name
gcloud application default credentials, and an account with GCS access to golang-org for bucket golang-release-staging
release-manager group membership on Gerrit

NOTE: all but the Gerrit permission are ensured by the bot on startup.