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

Setup jobs and dashboards for release-1.4 branch #8270

Closed
furkatgofurov7 opened this issue Mar 13, 2023 · 6 comments · Fixed by kubernetes/test-infra#29006
Closed

Setup jobs and dashboards for release-1.4 branch #8270

furkatgofurov7 opened this issue Mar 13, 2023 · 6 comments · Fixed by kubernetes/test-infra#29006
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@furkatgofurov7
Copy link
Member

What would you like to be added (User Story)?

Setup jobs and dashboards for release-1.4 branch in test-infra repository

Detailed Description

Soon, the release-1.4 branch is going to be created. Now we can setup the jobs in test-infra for that branch.
The steps to follow: https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#setup-jobs-and-dashboards-for-a-new-release-branch

Anything else you would like to add?

Part of #7672

Label(s) to be applied

/kind feature

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 13, 2023
@furkatgofurov7
Copy link
Member Author

/triage accepted
/assign

@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 Mar 13, 2023
@furkatgofurov7
Copy link
Member Author

@ykakarap @sbueringer @fabriziopandini release tasks document mentions the following:

Remove tests for old release branches according to our policy documented in [Support and guarantees](https://github.com/kubernetes-sigs/cluster-api/blob/main/CONTRIBUTING.md#support-and-guarantees) For example, let's assume we just created tests for v1.4, then we can now drop test coverage for the release-1.1 branch.

Do we have to drop the tests with the same PR where we are adding new tests for v1.4 or do it as a follow-up?

@furkatgofurov7
Copy link
Member Author

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

@sbueringer
Copy link
Member

sbueringer commented Mar 14, 2023

@ykakarap @sbueringer @fabriziopandini release tasks document mentions the following:

Remove tests for old release branches according to our policy documented in [Support and guarantees](https://github.com/kubernetes-sigs/cluster-api/blob/main/CONTRIBUTING.md#support-and-guarantees) For example, let's assume we just created tests for v1.4, then we can now drop test coverage for the release-1.1 branch.

Do we have to drop the tests with the same PR where we are adding new tests for v1.4 or do it as a follow-up?

We can do it in a follow-up.

@furkatgofurov7
Copy link
Member Author

We can do it in a follow-up.

Thanks for confirmation, I'll send a follow-up PR for removing them.

@furkatgofurov7
Copy link
Member Author

Thanks for confirmation, I'll send a follow-up PR for removing them.

@sbueringer tracked in #8281

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants