test-infra
test-infra copied to clipboard
kubernetes
Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations
What should be cleaned up or changed:
We should revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations to make sure values are still valid. This is especially important because we added stable4 version marker not so long ago. While I went through annotations when adding stable4, I think I might missed some of them, so double checking values to be sure would be nice.
For example, this annotation might be missing one periodic interval: https://github.com/kubernetes/test-infra/blob/2d42d0dc37b8c2cceccda393c8bb07d5d39eb7a5/config/jobs/kubernetes/sig-release/release-branch-jobs/1.27.yaml#L134
Provide any links for context:
See #29387 for more details
This should be done before removing jobs for 1.24
/priority important-soon /milestone v1.28 cc @kubernetes/release-engineering
@xmudrii: The provided milestone is not valid for this repository. Milestones in this repository: [someday, v1.24, v1.25]
Use /milestone clear to clear the milestone.
In response to this:
What should be cleaned up or changed:
We should revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations to make sure values are still valid. This is especially important because we added stable4 version marker not so long ago. While I went through annotations when adding stable4, I think I might missed some of them, so double checking values to be sure would be nice.
For example, this annotation might be missing one periodic interval: https://github.com/kubernetes/test-infra/blob/2d42d0dc37b8c2cceccda393c8bb07d5d39eb7a5/config/jobs/kubernetes/sig-release/release-branch-jobs/1.27.yaml#L134
Provide any links for context:
See #29387 for more details
This should be done before removing jobs for 1.24
/priority important-soon /milestone v1.28 cc @kubernetes/release-engineering
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.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I didn't notice any issue with these annotations for the past couple of releases, I think we should be all good now. /close
@xmudrii: Closing this issue.
In response to this:
I didn't notice any issue with these annotations for the past couple of releases, I think we should be all good now. /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-sigs/prow repository.