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

Update Prow to v20241122-ec19f2447, Boskos to v20241119-445d89e #557

Merged

Conversation

knative-prow-updater-robot
Copy link
Contributor

Multiple distinct us-docker.pkg.dev/k8s-infra-prow/images/ changes:

Commits Dates Images
kubernetes-sigs/prow@cc8d4cf...ec19f24 2024‑11‑16 → 2024‑11‑22 images/branchprotector, images/checkconfig, images/cherrypicker, images/clonerefs, images/config-bootstrapper, images/crier, images/deck, images/entrypoint, images/generic-autobumper, images/ghproxy, images/hook, images/horologium, images/initupload, images/mkpj, images/needs-rebase, images/peribolos, images/prow-controller-manager, images/sidecar, images/sinker, images/status-reconciler, images/tide

Multiple distinct gcr.io/k8s-staging-boskos/ changes:

Commits Dates Images
kubernetes-sigs/boskos@bc478df...445d89e 2024‑10‑28 → 2024‑11‑19 boskos, janitor, reaper

/cc

Multiple distinct us-docker.pkg.dev/k8s-infra-prow/images/ changes:

Commits | Dates | Images
--- | --- | ---
kubernetes-sigs/prow@cc8d4cf...ec19f24 | 2024‑11‑16 → 2024‑11‑22 | images/branchprotector, images/checkconfig, images/cherrypicker, images/clonerefs, images/config-bootstrapper, images/crier, images/deck, images/entrypoint, images/generic-autobumper, images/ghproxy, images/hook, images/horologium, images/initupload, images/mkpj, images/needs-rebase, images/peribolos, images/prow-controller-manager, images/sidecar, images/sinker, images/status-reconciler, images/tide

Multiple distinct gcr.io/k8s-staging-boskos/ changes:

Commits | Dates | Images
--- | --- | ---
kubernetes-sigs/boskos@bc478df...445d89e | 2024‑10‑28 → 2024‑11‑19 | boskos, janitor, reaper
Copy link

knative-prow bot commented Nov 25, 2024

@knative-prow-updater-robot: GitHub didn't allow me to request PR reviews from the following users: knative-prow-updater-robot.

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

In response to this:

Multiple distinct us-docker.pkg.dev/k8s-infra-prow/images/ changes:

Commits Dates Images
kubernetes-sigs/prow@cc8d4cf...ec19f24 2024‑11‑16 → 2024‑11‑22 images/branchprotector, images/checkconfig, images/cherrypicker, images/clonerefs, images/config-bootstrapper, images/crier, images/deck, images/entrypoint, images/generic-autobumper, images/ghproxy, images/hook, images/horologium, images/initupload, images/mkpj, images/needs-rebase, images/peribolos, images/prow-controller-manager, images/sidecar, images/sinker, images/status-reconciler, images/tide

Multiple distinct gcr.io/k8s-staging-boskos/ changes:

Commits Dates Images
kubernetes-sigs/boskos@bc478df...445d89e 2024‑10‑28 → 2024‑11‑19 boskos, janitor, reaper

/cc

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.

Copy link

knative-prow bot commented Nov 25, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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

@knative-prow knative-prow bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 25, 2024
@knative-prow knative-prow bot merged commit 7f03927 into knative:main Nov 25, 2024
17 checks passed
Copy link

knative-prow bot commented Nov 25, 2024

@knative-prow-updater-robot: Updated the following 2 configmaps:

  • job-config configmap in namespace default at cluster default using the following files:
    • key autobump-flaky-test-reporter.yaml using file prow/jobs/custom/autobump-flaky-test-reporter.yaml
    • key autobump-prow-tests.yaml using file prow/jobs/custom/autobump-prow-tests.yaml
    • key autobump-prow.yaml using file prow/jobs/custom/autobump-prow.yaml
    • key autodeploy-prow.yaml using file prow/jobs/custom/autodeploy-prow.yaml
    • key branchprotector.yaml using file prow/jobs/custom/branchprotector.yaml
    • key infra.yaml using file prow/jobs/custom/infra.yaml
    • key peribolos.yaml using file prow/jobs/custom/peribolos.yaml
  • config configmap in namespace default at cluster default using the following files:
    • key config.yaml using file prow/config.yaml

In response to this:

Multiple distinct us-docker.pkg.dev/k8s-infra-prow/images/ changes:

Commits Dates Images
kubernetes-sigs/prow@cc8d4cf...ec19f24 2024‑11‑16 → 2024‑11‑22 images/branchprotector, images/checkconfig, images/cherrypicker, images/clonerefs, images/config-bootstrapper, images/crier, images/deck, images/entrypoint, images/generic-autobumper, images/ghproxy, images/hook, images/horologium, images/initupload, images/mkpj, images/needs-rebase, images/peribolos, images/prow-controller-manager, images/sidecar, images/sinker, images/status-reconciler, images/tide

Multiple distinct gcr.io/k8s-staging-boskos/ changes:

Commits Dates Images
kubernetes-sigs/boskos@bc478df...445d89e 2024‑10‑28 → 2024‑11‑19 boskos, janitor, reaper

/cc

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
Labels
size/M Denotes a PR that changes 30-99 lines, ignoring generated files. skip-review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant