-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Migrate jobs away from deprecated bootstrap usage #20760
Comments
@spiffxp: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
@spiffxp: The label(s) 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. |
As an FYI, jobs that migrate away from bootstrap will lack an Infra-Commit column in testgrid: #20650. This is not a blocker to migration, and is probably a good thing (one less thing to bisect). I strongly suspect kubernetes/test-infra code being checked out in a job's container isn't actually necessary for the vast majority of jobs that make the switch away from bootstrap. |
Things to help track our status:
|
/kind cleanup |
xref: #30846 |
This is an umbrella issue to track migrating job configs away from bootstrap and instead use pod-utils.
Bootstrap has been deprecated for a few years at this point, and jobs that use bootstrap.py have been unsupported by test-infra-oncall for at least 1.5 years (ref: #14392). Pod-utils are the documented and supported way of writing prowjobs: https://github.com/kubernetes/test-infra/tree/master/config/jobs#job-cookbook
One way to be helpful: PR in a guide on how to do this! Relevant content to source from:
Another way to help: produce a tool, script or dashboard that keeps track of what has and has not been migrated. We could either link to its results from this issue, or periodically update this issue with the results.
The most concrete way to help: migrate the jobs you or your SIG owns
/lifecycle frozen
/priority important-longterm
/sig testing
Once we have tracking of which sigs own jobs that use bootstrap, we can tag with appropriate sigs.
/area jobs
/area bootstrap
/area prow/pod-utils
/help
The text was updated successfully, but these errors were encountered: