Skip to content

[build] Standardize docker image tarball suffixes for architectures #224969

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

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

Conversation

jbudz
Copy link
Member

@jbudz jbudz commented Jun 23, 2025

Previously amd64 images didn't have a suffix, and arm64 images were suffixed with aarch64. This updates all references to use amd64 or arm64.

Closes #222990

Previously amd64 images didn't have a suffix, and arm64 images were
suffixed with aarch64.  This updates all references to use amd64 or
arm64.

Closes elastic#222990
@jbudz jbudz requested a review from a team as a code owner June 23, 2025 22:01
@jbudz jbudz added Team:Operations Team label for Operations Team release_note:skip Skip the PR/issue when compiling release notes labels Jun 23, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@jbudz jbudz added the backport:all-open Backport to all branches that could still receive a release label Jun 23, 2025
@jbudz jbudz requested a review from alina-bacalete June 23, 2025 22:02
@jbudz
Copy link
Member Author

jbudz commented Jun 23, 2025

buildkite test this

@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Jest Tests #18 / multi select filter should render the amount of options available

Metrics [docs]

✅ unchanged

Copy link
Contributor

@Ikuni17 Ikuni17 left a comment

Choose a reason for hiding this comment

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

Do you think it's worth standardizing all the artifact names not just the Docker images at this point?

@jbudz
Copy link
Member Author

jbudz commented Jun 24, 2025

Do you think it's worth standardizing all the artifact names not just the Docker images at this point?

I'll leave this for @alina-bacalete. The one exception I'm aware of is aarch64 should be used by convention for rpm packages.

@alina-bacalete
Copy link

Do you think it's worth standardizing all the artifact names not just the Docker images at this point?

I'll leave this for @alina-bacalete. The one exception I'm aware of is aarch64 should be used by convention for rpm packages.

Hello! I don't have a strong opinion on standardizing all the artifact names besides the Docker images, I do believe we should strive for consistency and standard naming conventions across products, but ultimately I think this is a decision for your team to make. Thank you for raising the PR!

Please see here the related infra PR for these changes: https://github.com/elastic/infra/pull/42183 and let's sync when merging to be sure we have all the pieces in place. TIA!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:all-open Backport to all branches that could still receive a release ci:build-all-platforms ci:build-os-packages release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Standardize image artifact name
4 participants