Add export PLATFORMS=all to post-submit jobs for bridge-marker

[ashokpariya0]

This update ensures that the PLATFORMS environment variable is set to "all" before executing the make docker-build docker-push command in both main-bridge-marker and release-bridge-marker jobs. This change enables building multi-platform supported bridge marker image.

What this PR does / why we need it:
This commit (892ccdd) enables multi-platform support. By default, the image is built based on the host architecture. To build a multi-platform image that supports amd64, arm64, and s390x, the PLATFORMS=all environment variable needs to be exported before running the make docker-build command.

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.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

None

[kubevirt-bot]

Hi @ashokpariya0. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[oshoval]

Thanks
/lgtm

@brianmcarey can you please take a look ?

[brianmcarey]

/approve

thanks @ashokpariya0 !

[kubevirt-bot]

[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

Needs approval from an approver in each of these files:

• github/ci/prow-deploy/files/jobs/kubevirt/bridge-marker/OWNERS [brianmcarey]

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

[kubevirt-bot]

@ashokpariya0: Updated the job-config configmap in namespace kubevirt-prow at cluster default using the following files:

• key bridge-marker-postsubmits.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/bridge-marker/bridge-marker-postsubmits.yaml

In response to this:

This update ensures that the PLATFORMS environment variable is set to "all" before executing the make docker-build docker-push command in both main-bridge-marker and release-bridge-marker jobs. This change enables building multi-platform supported bridge marker image.

What this PR does / why we need it:
This commit (892ccdd) enables multi-platform support. By default, the image is built based on the host architecture. To build a multi-platform image that supports amd64, arm64, and s390x, the PLATFORMS=all environment variable needs to be exported before running the make docker-build command.

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.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

None

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.