Closed dhiller closed 1 month ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
/uncc @enp0s3 @phoracek /cc @brianmcarey
/uncc @tiraboschi @vladikr
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: brianmcarey
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@dhiller: Updated the job-config
configmap in namespace kubevirt-prow
at cluster default
using the following files:
project-infra-postsubmits.yaml
using file github/ci/prow-deploy/files/jobs/kubevirt/project-infra/project-infra-postsubmits.yaml
What this PR does / why we need it:
The list [1] is outdated - the job definition needs to get updated manually for the release branches.
This change adds a shell generation for the last three release branch configs so we avoid dealing with this manually.
Successful run here [2].
[1] https://storage.googleapis.com/kubevirt-prow/reports/e2ejobs/kubevirt/kubevirt/presubmits.html [2] https://prow.ci.kubevirt.io/log?container=test&id=1809192423146917888&job=post-project-infra-kubevirt-e2e-jobs-overview
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged): Fixes #Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR. Approvers are expected to review this list.
Release note: