Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for s390x architecture in GitHub Actions workflows. #337

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ashokpariya0
Copy link

Updated GitHub Actions workflows to include linux/s390x in BUILD_PLATFORMS. Modified hack/install-go.sh to dynamically select the appropriate Go tarball based on the system's architecture(amd64, arm64, or others), allowing better support for multi-architecture environments.

What this PR does / why we need it:
these changes enhances GitHub Actions workflows by adding linux/s390x to BUILD_PLATFORMS.
also updates hack/install-go.sh to automatically select the correct Go tarball based on the system architecture (amd64, arm64, or others), improving support for multi-architecture environments.

Special notes for your reviewer:

Release note:

None

Updated GitHub Actions workflows to include linux/s390x in BUILD_PLATFORMS.
Modified hack/install-go.sh to dynamically select the appropriate Go tarball
based on the system's architecture(amd64, arm64, or others), allowing better
support for multi-architecture environments.

Signed-off-by: Ashok Pariya <[email protected]>
@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Dec 4, 2024
@kubevirt-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ashokpariya0
Once this PR has been reviewed and has the lgtm label, please assign phoracek for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

@kubevirt-bot
Copy link
Collaborator

Hi @ashokpariya0. Thanks for your PR.

I'm waiting for a k8snetworkplumbingwg member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@ashokpariya0
Copy link
Author

@oshoval @0xFelix could you please take a look at pr.

@@ -2,7 +2,8 @@

destination=$1
version=$(curl -s https://go.dev/dl/?mode=json | jq -r ".[0].version")
tarball=$version.linux-amd64.tar.gz
arch=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that required? IIUC the binaries for all platforms are cross-compiled on amd64?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.that's correct.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you're asking why we use the sed command, here's the explanation:
The terms "x86_64" and "amd64" refer to the same architecture. However, the uname -m command returns "x86_64" to describe this architecture. On the other hand, the Go programming language uses the term "amd64" for this architecture. Therefore, to ensure consistency with Go and cross-compilation setups, we use the sed command to rename "x86_64" to "amd64".

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I got that. Just asking if we need this change or if we can continue to cross compile on amd64.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need this change to build on s390x or other platforms.

@0xFelix
Copy link
Contributor

0xFelix commented Dec 4, 2024

/ok-to-test

@kubevirt-bot
Copy link
Collaborator

@0xFelix: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

@0xFelix
Copy link
Contributor

0xFelix commented Dec 4, 2024

@oshoval Please mark this as ok-to-test

@phoracek
Copy link
Member

phoracek commented Dec 4, 2024

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dco-signoff: yes Indicates the PR's author has DCO signed all their commits. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. release-note-none Denotes a PR that doesn't merit a release note.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants