[CI] Fixed container images packaging

[pazone]

What does this PR do?

Fixed container image packaging by setting proper packaging variables
We now have 9 packaging steps:

Packaging: linux/amd64 rpm

Artifacts :

• elastic-agent-9.0.0-SNAPSHOT-x86_64.rpm
• elastic-agent-9.0.0-SNAPSHOT-x86_64.rpm.sha512

Packaging: linux/arm64 rpm

Artifacts :

• elastic-agent-9.0.0-SNAPSHOT-aarch64.rpm
• elastic-agent-9.0.0-SNAPSHOT-aarch64.rpm.sha512

Packaging: linux/amd64 deb

Artifacts :

• elastic-agent-9.0.0-SNAPSHOT-amd64.deb
• elastic-agent-9.0.0-SNAPSHOT-amd64.deb.sha512

Packaging: linux/arm64 deb

Artifacts:

• elastic-agent-9.0.0-SNAPSHOT-arm64.deb
• elastic-agent-9.0.0-SNAPSHOT-arm64.deb.sha512

Packaging: linux/amd64 tar.gz

Artifacts:

• elastic-agent-9.0.0-SNAPSHOT-linux-x86_64.tar.gz
• elastic-agent-9.0.0-SNAPSHOT-linux-x86_64.tar.gz.sha512

Packaging: linux/arm64 tar.gz

Artifacts:

• elastic-agent-9.0.0-SNAPSHOT-linux-arm64.tar.gz
• elastic-agent-9.0.0-SNAPSHOT-linux-arm64.tar.gz.sha512

Packaging: Containers linux/amd64

14 amd64 images. See the build

Packaging: Containers linux/arm64

14 arm64 images. See the build

Packaging: windows/amd64 zip

• elastic-agent-9.0.0-SNAPSHOT-windows-x86_64.zip
• elastic-agent-9.0.0-SNAPSHOT-windows-x86_64.zip.sha512

Why is it important?

The container images will be used by k8s integration tests instead of rebuilding them.

Checklist

• I have read and understood the pull request guidelines of this project.
• 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/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[pazone]

Build matrix is not used because we need unique step keys

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b ci_fix_packaging_containers upstream/ci_fix_packaging_containers
git merge upstream/main
git push upstream ci_fix_packaging_containers

[pazone]

Build takes too long because of the emulation

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: cd3e102

Failed CI Steps

• Packaging: Containers linux/arm64

History

• 💔 Build #17534 failed 0a73c85
• 💔 Build #17533 failed e8e4546
• 💔 Build #17515 failed 841ab70
• 💔 Build #17473 failed 57591b2
• 💔 Build #17405 failed 08efd9f

cc @pazone

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube