Run hack/bump-prow.sh

[kubevirt-bot]

Bump Prow

/cc @kubevirt/prow-job-taskforce

[kubevirt-bot]

@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/test-infra repository.

[dhiller]

@dhiller's review-bot says:

• 👍 This looks like a simple prow job image bump.
• 👎 This doesn't look like a simple prow autobump.

I found suspicious hunks:

github/ci/prow-deploy/kustom/base/manifests/test_infra/current/prowjob-crd/prowjob_customresourcedefinition.yaml

               reporter_config:
                 description: ReporterConfig holds reporter-specific configuration
                 properties:
+                  resultstore:
+                    description: 'TODO: This config is used only for alpha testing
+                      and will likely move to ProwJobDefaults for flexibility.'
+                    properties:
+                      project_id:
+                        description: Specifies the ResultStore InvocationAttributes.ProjectId,
+                          used for various quota and GUI access control purposes.
+                          In practice, it is generally the same as the Google Cloud
+                          Project ID or number of the job's GCS storage bucket. Required
+                          to write job results to ResultStore.
+                        type: string
+                    type: object
                   slack:
                     properties:
                       channel:

This PR does not satisfy at least one automated review criteria.

Holding this PR for further manual action to occur.

/hold

Note: botreview (#2448) is a Work In Progress!

[dhiller]

/approve

/unhold

[kubevirt-bot]

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

• OWNERS [dhiller]

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: 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-postsubmits.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/project-infra/project-infra-postsubmits.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/test-infra repository.