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.

Sign up for GitHub

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

Jump to bottom

Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations #29388

Open
xmudrii opened this issue Apr 28, 2023 · 8 comments
Open

Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations #29388

xmudrii opened this issue Apr 28, 2023 · 8 comments
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@xmudrii
Copy link
Member

xmudrii commented Apr 28, 2023

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:

test-infra/config/jobs/kubernetes/sig-release/release-branch-jobs/1.27.yaml

Line 134 in 2d42d0d

fork-per-release-periodic-interval: 6h 24h

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 xmudrii added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Apr 28, 2023
@k8s-ci-robot
Copy link
Contributor

@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:

test-infra/config/jobs/kubernetes/sig-release/release-branch-jobs/1.27.yaml

Line 134 in 2d42d0d

fork-per-release-periodic-interval: 6h 24h

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.

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 28, 2023
@xmudrii
Copy link
Member Author

xmudrii commented Apr 28, 2023

/sig release

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 28, 2023
@xmudrii xmudrii mentioned this issue Apr 28, 2023
Merged
@jeremyrickard jeremyrickard mentioned this issue Aug 30, 2023
Merged
@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Jan 19, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2024
@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 18, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Apr 19, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 19, 2024
@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 18, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Jul 22, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xmudrii @k8s-ci-robot @k8s-triage-robot