Skip to content

Run hack/bump-prow.sh #3749

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
Merged
merged 1 commit into from
Feb 10, 2025
Merged

Run hack/bump-prow.sh #3749

merged 1 commit into from
Feb 10, 2025

Conversation

kubevirt-bot
Copy link
Contributor

Bump Prow

/cc @kubevirt/prow-job-taskforce

@kubevirt-bot
Copy link
Contributor Author

@kubevirt-bot: GitHub didn't allow me to request PR reviews from the following users: kubevirt/prow-job-taskforce.

Note that only kubevirt members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Bump Prow

/cc @kubevirt/prow-job-taskforce

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.

@kubevirt-bot kubevirt-bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/M labels Nov 8, 2024
brianmcarey
brianmcarey reviewed Nov 8, 2024
View reviewed changes
Copy link
Member

@brianmcarey brianmcarey left a comment

Choose a reason for hiding this comment

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

/hold

this reverts last weeks manual bump

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 8, 2024
@kubevirt-bot kubevirt-bot force-pushed the prow-autobump branch 2 times, most recently from 97151d8 to 390db0c Compare November 29, 2024 06:10
@kubevirt-bot kubevirt-bot force-pushed the prow-autobump branch 2 times, most recently from 1255bcb to c936fa8 Compare December 27, 2024 06:10
@kubevirt-bot
Copy link
Contributor Author

kubevirt-bot commented Jan 10, 2025 •
edited
Loading

@kubevirt-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-project-infra-lint 6eccc06 link true /test pull-project-infra-lint

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. I understand the commands that are listed here.

@kubevirt-bot kubevirt-bot force-pushed the prow-autobump branch 2 times, most recently from f41e9be to 7aaf3a2 Compare January 31, 2025 06:10
@dhiller
Copy link
Contributor

dhiller commented Feb 3, 2025

Changed the auto bump process with this: #3932

After merge this PR can be closed.

@dhiller dhiller mentioned this pull request Feb 3, 2025
Merged
@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 3, 2025
@kubevirt-bot
Run hack/bump-prow.sh
Loading
Loading status checks…
85acaa6 
Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
@kubevirt-bot kubevirt-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 7, 2025
dhiller
dhiller reviewed Feb 7, 2025
View reviewed changes
Copy link
Contributor

@dhiller dhiller left a comment

Choose a reason for hiding this comment

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

/hold

need to verify the lens issue is fixed

@dhiller
Copy link
Contributor

dhiller commented Feb 10, 2025

/hold

need to verify the lens issue is fixed

Encountered issue was reverted with kubernetes-sigs/prow#371. Let's retry.

/unhold

@kubevirt-bot kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 10, 2025
dhiller
dhiller approved these changes Feb 10, 2025
View reviewed changes
Copy link
Contributor

@dhiller dhiller left a comment

Choose a reason for hiding this comment

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

/approve

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2025
@kubevirt-bot
Copy link
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

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

The pull request process is described here

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2025
@kubevirt-bot kubevirt-bot merged commit 12542b9 into kubevirt:main Feb 10, 2025
5 checks passed
@kubevirt-bot
Copy link
Contributor Author

@kubevirt-bot: Updated the following 2 configmaps:

  • job-config configmap in namespace kubevirt-prow at cluster default using the following files:
    • key project-infra-periodics.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/project-infra/project-infra-periodics.yaml
    • key project-infra-presubmits.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/project-infra/project-infra-presubmits.yaml
  • config configmap in namespace kubevirt-prow at cluster default using the following files:
    • key config.yaml using file github/ci/prow-deploy/kustom/base/configs/current/config/config.yaml

In response to this:

Bump Prow

/cc @kubevirt/prow-job-taskforce

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@brianmcarey brianmcarey

@dhiller dhiller

Assignees

@dhiller dhiller

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. size/M
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@kubevirt-bot @dhiller @brianmcarey