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

Make krel fast-forward work for other repositories like k/website #3380

Open
saschagrunert opened this issue Nov 29, 2023 · 8 comments · Fixed by #3445
Open

Make krel fast-forward work for other repositories like k/website #3380

saschagrunert opened this issue Nov 29, 2023 · 8 comments · Fixed by #3445
Assignees
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@saschagrunert
Copy link
Member

There is a sync job in place which fast-forwards the kubernetes/kubernetes release-1.x branch from master until the final (non-prerelease) tag exists on it. The job runs periodically in prow and does basically nothing when we're not in code freeze: https://testgrid.k8s.io/sig-release-releng-blocking#git-repo-kubernetes-fast-forward

The idea is to re-use the logic for other repositories like k/website to sync the documentation development branch during the release cycle. We have to make the tool more flexible from a CLI perspective and double check the code paths for possible adaptations.

The entrypoint for the code of krel fast-forward is there: https://github.com/kubernetes/release/blob/master/cmd/krel/cmd/ff.go

@saschagrunert saschagrunert added kind/feature Categorizes issue or PR as related to a new feature. sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Nov 29, 2023
@saschagrunert
Copy link
Member Author

@cpanato volunteered to work on this

/assign @cpanato

@saschagrunert saschagrunert added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Nov 30, 2023
@cpanato
Copy link
Member

cpanato commented Nov 30, 2023

this will require some code changes I will start working on this part

k8s-ci-robot added a commit that referenced this issue Feb 12, 2024
adapt krel/ff to run with other repositories that are not only k/k
@cpanato
Copy link
Member

cpanato commented Feb 13, 2024

not yet done
/reopen

@k8s-ci-robot k8s-ci-robot reopened this Feb 13, 2024
@k8s-ci-robot
Copy link
Contributor

@cpanato: Reopened this issue.

In response to this:

not yet done
/reopen

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-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 May 13, 2024
@cpanato
Copy link
Member

cpanato commented May 13, 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 May 13, 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 Aug 11, 2024
@xmudrii
Copy link
Member

xmudrii commented Aug 12, 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 Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants