Skip to content

WIP: scripts for common devtasks#17390

Open
justinsb wants to merge 1 commit intokubernetes:masterfrom
justinsb:devtasks
Open

WIP: scripts for common devtasks#17390
justinsb wants to merge 1 commit intokubernetes:masterfrom
justinsb:devtasks

Conversation

@justinsb
Copy link
Member

@justinsb justinsb commented May 3, 2025

No description provided.

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 3, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented May 3, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign johngmyers for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 3, 2025
@k8s-ci-robot k8s-ci-robot requested review from hakman and zetaab May 3, 2025 21:15
@justinsb
Copy link
Member Author

justinsb commented May 3, 2025

I thought I sent these previously; I've been using these to automate releases for a while. I'm marking WIP because at this point I should verify that they (still) work by doing a release.

My guess is that was what went wrong last time, I intended to send the PR after I verified and simply forgot once I got through the release process. So this time I'm opening the WIP in advance :-)

rifelpet
rifelpet reviewed May 7, 2025
View reviewed changes
devtasks/automation/stage_github_release/stage_github_release.sh
gsutil rsync -r gs://k8s-staging-kops/kops/releases/${VERSION}/ ${WORKDIR}/releases/${VERSION}/

git checkout v$VERSION
${shipbot} -tag v${VERSION} -config .shipbot.yaml -src ${WORKDIR}/releases/${VERSION}/
Copy link
Member

@rifelpet rifelpet May 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There might be a bug in shipbot - The 1.32.0 release notes include PRs going back to Kops 1.19 like #10049

Copy link
Member

@hakman hakman Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shipbot only copies the binaries to the release, release notes were added with a different tool, no longer in use.

@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 5, 2025

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs 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 PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR 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 5, 2025
@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 4, 2025

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs 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 PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 4, 2025
@hakman
Copy link
Member

hakman commented Sep 4, 2025

/remove-lifecycle rotten
Ping @justinsb

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 4, 2025
@k8s-triage-robot
Copy link

k8s-triage-robot commented Dec 3, 2025

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs 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 PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR 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 Dec 3, 2025
@hakman
Copy link
Member

hakman commented Dec 3, 2025

/test all
/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 Dec 3, 2025
@hakman hakman closed this Dec 3, 2025
@hakman hakman reopened this Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@rifelpet rifelpet rifelpet left review comments

@hakman hakman Awaiting requested review from hakman

@zetaab zetaab Awaiting requested review from zetaab

Assignees

No one assigned

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@justinsb @k8s-ci-robot @k8s-triage-robot @hakman @rifelpet