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

Removing jobs for unsupported release branches #8039

Closed
2 tasks done
sbueringer opened this issue Feb 1, 2023 · 13 comments
Closed
2 tasks done

Removing jobs for unsupported release branches #8039

sbueringer opened this issue Feb 1, 2023 · 13 comments
Assignees
Labels
area/testing Issues or PRs related to testing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sbueringer
Copy link
Member

sbueringer commented Feb 1, 2023

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:

Let's only keep jobs of the currently supported releases and 1 additional release in case we have to do an emergency patch release.

Now let's apply the policy to our current jobs:

  • We keep the jobs for:
    • release-1.3 => still supported
    • release-1.2 => still supported
    • release-1.1 => we keep the job for one more release cycle, they will be dropped after the v1.4.0 release
  • We remove the jobs for:
    • release-1.0, release-0.4, release-0.3: they are out of support for longer than one release cycle.

Tasks

/kind cleanup
/area testing

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/testing Issues or PRs related to testing needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 1, 2023
@sbueringer sbueringer self-assigned this Feb 1, 2023
@furkatgofurov7
Copy link
Member

furkatgofurov7 commented Feb 1, 2023

+1
I am also happy to help with the clean up, once we agree with all community members (including downstream).

@sbueringer
Copy link
Member Author

sbueringer commented Feb 1, 2023

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

@sbueringer
Copy link
Member Author

cc @kubernetes-sigs/cluster-api-release-team

@fabriziopandini
Copy link
Member

/triage accepted
yay! this is a nice cleanup, it contributes to the log term health of the projects and it also helps the K8s community in the effort of containing infra costs.

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 2, 2023
@CecileRobertMichon
Copy link
Contributor

+1

@cpanato
Copy link
Member

cpanato commented Feb 3, 2023

+1 let me know if i can open the PR to remove those

@elmiko
Copy link
Contributor

elmiko commented Feb 6, 2023

+1, happy to help review

@sbueringer
Copy link
Member Author

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.

@sbueringer
Copy link
Member Author

sbueringer commented Feb 21, 2023

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)

@furkatgofurov7
Copy link
Member

@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

@furkatgofurov7
Copy link
Member

@sbueringer @cpanato PTAL: kubernetes/test-infra#28808

@sbueringer
Copy link
Member Author

All done.

Thx everyone!

/close

@k8s-ci-robot
Copy link
Contributor

@sbueringer: Closing this issue.

In response to this:

All done.

Thx everyone!

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

7 participants