Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/build: automatically start building subrepos for new release branches #21556

Closed
s-mang opened this issue Aug 22, 2017 · 1 comment
Closed

x/build: automatically start building subrepos for new release branches #21556

s-mang opened this issue Aug 22, 2017 · 1 comment
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Unreleased

Comments

@s-mang
Copy link
Contributor

s-mang commented Aug 22, 2017

currently, a new release tag entity must be manually added to datastore before subrepos will be built and displayed on build.golang.org's index page.

this should be automated.

cc @rsc @broady
@gopherbot gopherbot added this to the Unreleased milestone Aug 22, 2017
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Aug 22, 2017
@dmitshur dmitshur added the NeedsFix The path to resolution is known, but the work has not been done. label Feb 29, 2020
@dmitshur
Copy link
Contributor

See also #34097.

This has been automated by now. When we released Go 1.14, we didn't have to do any manual work to get release-branch.go1.14 to show up on build.golang.org, and for release-branch.go1.12 to get hidden (/cc @cagedmantis @toothrot).

It was done in CL 194643 (/cc @bradfitz). Closing.

@dmitshur dmitshur mentioned this issue Feb 29, 2020
Closed
@golang golang locked and limited conversation to collaborators Feb 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@dmitshur @s-mang @gopherbot