-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Removing jobs for unsupported release branches #8039
Comments
+1 |
Thx! Sounds good. I've assigned the issue to myself in the sense of that I want to ensure that the issue makes progress / is implemented. Happy to delegate the implementation / collaborate on the implementation |
cc @kubernetes-sigs/cluster-api-release-team |
/triage accepted |
+1 |
+1 let me know if i can open the PR to remove those |
+1, happy to help review |
I've opened a PR to document the policy and update the release tasks: #8118 Once this PR is merged someone can open a PR to drop the jobs. |
I'll merge #8118 tomorrow. @furkatgofurov7 @cpanato One of you can prepare the PR to drop the jobs for <= v1.0 if you want. (including the dashboards) |
@sbueringer sure, I'll send a PR today |
All done. Thx everyone! /close |
@sbueringer: Closing this issue. 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. |
Context
Currently we run tests for all release branches since v0.3, but actually supported are only v1.2 and v1.3.
Motivation
Let's focus on maintaining test jobs of relevant releases. It's not worth the effort to maintain branches of releases which have been out of supported for a while. Especially as they start failing over time for reasons unrelated to Cluster API (e.g. registry migration).
Proposal
Policy:
Now let's apply the policy to our current jobs:
Tasks
/kind cleanup
/area testing
The text was updated successfully, but these errors were encountered: