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

Backport of build: Create arm64 packages as well into release/1.2.x #3645

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #3428 to be assessed for backporting due to the inclusion of the label backport/1.2.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@david-yu
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-k8s/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Changes proposed in this PR

During the CRT on-boarding, packaging for other Linux architectures (arm64) was
not enabled. This change adds packaging support for those architectures. I've
specifically opted not to include 32-bit.

Other related updates:

  • To make future support a bit easier, I've enabled the build workflow from
    releng prefixed branches.
  • Using qemu emulation for testing package installs on other architectures,
    thus allowing us to validate the binaries work as intended
  • Minor alteration to the package install tests to use yum instead of rpm

Note: I tried to add 386/arm packages but pivoted away. There's something suspicious with the 386 binary specifically (see comments). Since usage of that architecture is low, I punted.

How I've tested this PR

Please note, these packages have not been extensively tested on their respective platforms. I did update the pipeline to run the smoke test (consul version) against the arm64 packages in an arm64 user-space. So I think it's in a good place.

How I expect reviewers to test this PR

Download builds and test in the same manner existing binaries are tested. Docker containers would be sufficient.

Checklist

Related

See #1132.
Related to hashicorp/releng-support#178.


Overview of commits

@hashicorp-cla
Copy link

hashicorp-cla commented Feb 16, 2024

CLA assistant check
All committers have signed the CLA.

@david-yu
Copy link
Contributor

This probably needs to be manually backported as the automatic backport failed.

@dekimsey dekimsey force-pushed the backport/releng/package-additional-linux-architectures/personally-ready-heron branch from 6fa4df6 to 9fa4575 Compare February 20, 2024 19:14
@dekimsey dekimsey marked this pull request as ready for review February 20, 2024 19:14
During the CRT on-boarding, packaging for other Linux architectures (arm64) was
not enabled. This change adds packaging support for those architectures. I've
specifically opted not to include 32-bit.

See #1132.
Related to hashicorp/releng-support#178.

Other related updates:

 - To make future support a bit easier, I've enabled the build workflow from
   releng prefixed branches.
 - Using qemu emulation for testing package installs on other architectures,
   thus allowing us to validate the binaries work as intended
 - Minor alteration to the package install tests to use yum instead of rpm
@dekimsey dekimsey force-pushed the backport/releng/package-additional-linux-architectures/personally-ready-heron branch from 9fa4575 to da8336f Compare February 20, 2024 19:19
@david-yu david-yu enabled auto-merge (squash) February 20, 2024 19:23
@david-yu david-yu merged commit ffb3219 into release/1.2.x Feb 20, 2024
19 of 43 checks passed
@david-yu david-yu deleted the backport/releng/package-additional-linux-architectures/personally-ready-heron branch February 20, 2024 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants