ci: periodic pipeline can perform a dry run of the promote step

[nestoracunablanco]

This approach allows for code reuse, enabling testing of different architectures without the need to promote changes.

Release note:

NONE

[nestoracunablanco]

Can you give an example set of commands that this helps with?

Sure, when we run it using the environment variable PROMOTE_DRY_RUN=true, it allows us to periodically run tests for other architectures without needing to publish anything. A valid use case could be to run tests for ARM and s390x with this option, and if everything goes well, run tests for AMD64 and publish the images.

There is also a PR in the pipeline for project-infra, which will be opened for discussion if this change is approved.

What do you think?

[0xFelix]

Is it because we can't have a single pipeline that builds and tests all artifacts for a given containerdisk Entry?

[nestoracunablanco]

Yes, the issue is that kubevirtci, with its default parameters, starts a Kubernetes cluster on the same machine. This means that only one architecture can be tested without complicating the code. This setup could allow for periodic jobs for other architectures that do not publish images.

[nestoracunablanco]

/retest

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0xFelix

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~~ [0xFelix]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[nestoracunablanco]

@akrejcir what do you think about this change?

[akrejcir]

/lgtm