-
Notifications
You must be signed in to change notification settings - Fork 378
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
Update go version playbook with information about creating and running canary presubmit jobs #1972
Comments
Hi @liggitt |
Sure, open for anyone to take, thanks |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What would you like to be added:
Update https://github.com/kubernetes/sig-release/blob/master/release-engineering/handbooks/go.md to include information about bumping the go version in the canary test image and running the canary presubmit jobs
Why is this needed:
When bumping minor go versions, we always need to ensure CI passes on the new version before merging.
We have a canary test image that can be built with the new go version, and canary {unit,verify,integration,dependencies} presubmit jobs that use the new image, but https://github.com/kubernetes/sig-release/blob/master/release-engineering/handbooks/go.md does not include information about updating the canary image or triggering those tests.
Making that info part of the playbook would make sure the person driving the update knows those tools are available and makes use of them prior to merge.
cc @dims @justaugustus
The text was updated successfully, but these errors were encountered: