kubevirt|cdi, mirroring: run //robots/cmd/uploader:uploader as postsubmit for main and release branches #3097
Description
CentOS dependencies are sometimes removed from the mirror, which leads to build failures if the rpm mirroring has not uploaded them:
ERROR: /home/prow/go/src/github.com/kubevirt/kubevirt/rpm/BUILD.bazel:1619:8: //rpm:sandboxroot_x86_64 depends on @kernel-headers-0__5.14.0-375.el9.x86_64//rpm:rpm in repository @kernel-headers-0__5.14.0-375.el9.x86_64 which failed to fetch. no such package '@kernel-headers-0__5.14.0-375.el9.x86_64//rpm': java.io.IOException: Error downloading [http://mirror.stream.centos.org/9-stream/AppStream/x86_64/os/Packages/kernel-headers-5.14.0-375.el9.x86_64.rpm] to /tmp/cache/bazel/18316b1300bb8985bc913139d5cc6323/external/kernel-headers-0__5.14.0-375.el9.x86_64/rpm/downloaded: GET returned 404 Not Found
We should run the uploader prowjob1 for main and release branches as postsubmit to directly upload new dependencies to gcs so that this is backed up.
For this we need to split the one job into three and move each one in their own repository.
Concerns:
- we might need to manually update the release branches as IIRC that
branches:doesn't allow wildcards - PR's must be created against the correct branch, we need to use
-TwithPULL_BASE_REF
Footnotes
Metadata
Metadata
Assignees
Labels
Issues and PRs concerning KubeVirt Prow, i.e. configuration, setup etc.Identifies an issue that has been specifically created or selected for new contributors.Indicates that an issue or PR should not be auto-closed due to staleness.Indicate that the issue or PR is a lower priority and can be worked on in the futureIndicates an issue or PR is ready to be actively worked on.