kubevirt|cdi, mirroring: run //robots/cmd/uploader:uploader as postsubmit for main and release branches

[dhiller]

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

source

We should run the uploader prowjob¹ 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 -T with PULL_BASE_REF

Footnotes

1. https://github.com/kubevirt/project-infra/blob/f9b523d3ae40c184ef11dffe9299dbc0f6791122/github/ci/prow-deploy/files/jobs/kubevirt/project-infra/project-infra-periodics.yaml#L214 ↩

[dhiller]

See kubevirt/kubevirt#10591 and kubevirt/kubevirt#10812 as an example.

[dhiller]

FYI @brianmcarey

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[akalenyu]

/remove-lifecycle stale

[dhiller]

/area prow

[dhiller]

/good-first-issue

[kubevirt-bot]

@dhiller:
This request has been marked as suitable for new contributors.

Guidelines

• No Barrier to Entry
• Clear Task
• Solution Explained
• Provides Context
• Identifies Relevant Code
• Gives Examples
• Ready to Test
• Goldilocks priority
• Up-To-Date

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

[akalenyu]

/reopen

[kubevirt-bot]

@akalenyu: Reopened this issue.

In response to this:

/reopen

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]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

[dhiller]

/reopen
/remove-lifecycle rotten
/lifecycle frozen

[kubevirt-bot]

@dhiller: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
/lifecycle frozen

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.