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

fix: use multiarch ARM Docker images on any architecture #31779

Merged
merged 1 commit into from
Jun 3, 2022

Conversation

kuisathaverat
Copy link
Contributor

@kuisathaverat kuisathaverat commented May 30, 2022

What does this PR do?

Remove a workaround added to force to use ARM Docker images on ARM architectures to build ARM binaries.

Why is it important?

This workaround is no longer need on the golang-crossbuild Docker images, we publish multiarch Docker images for the arm flavor.

Checklist

  • My code follows the style guidelines of this project
  • [] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files
  • [ ] I have added tests that prove my fix is effective or that my feature works
  • [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • [ ]

How to test this PR locally

on an ARM64 machine run the command PLATFORMS="linux/arm64" mage package on any beat.

Related issues

Use cases

Screenshots

Logs

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 30, 2022
@kuisathaverat kuisathaverat added ci Team:Automation Label for the Observability productivity team labels May 30, 2022
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 30, 2022
@kuisathaverat kuisathaverat requested review from a team May 30, 2022 16:51
@elasticmachine
Copy link
Collaborator

elasticmachine commented May 30, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-06-01T12:08:12.862+0000

  • Duration: 75 min 52 sec

Test stats 🧪

Test Results
Failed 0
Passed 22260
Skipped 1935
Total 24195

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@kuisathaverat
Copy link
Contributor Author

/package

1 similar comment
@kuisathaverat
Copy link
Contributor Author

/package

@kuisathaverat
Copy link
Contributor Author

kuisathaverat commented May 30, 2022

This requires Go 1.18.2, the main branch is still on 1.17.10

@kuisathaverat
Copy link
Contributor Author

/test

@kuisathaverat
Copy link
Contributor Author

/test

@kuisathaverat kuisathaverat merged commit 7509551 into elastic:main Jun 3, 2022
@kuisathaverat kuisathaverat added the backport-v8.3.0 Automated backport with mergify label Jun 3, 2022
mergify bot pushed a commit that referenced this pull request Jun 3, 2022
zmoog pushed a commit that referenced this pull request Jun 28, 2022
kuisathaverat added a commit that referenced this pull request Jun 28, 2022
…1819)

(cherry picked from commit 7509551)

Co-authored-by: Ivan Fernandez Calvo <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v8.3.0 Automated backport with mergify ci Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants