[8.18](backport #6972) [CI] Fixed container images packaging

[mergify]

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?
• ...

---

This is an automatic backport of pull request #6972 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 14943f0 has failed:

On branch mergify/bp/8.18/pr-6972
Your branch is up to date with 'origin/8.18'.

You are currently cherry-picking commit 14943f0fc.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/bk.integration.pipeline.yml
	modified:   dev-tools/mage/crossbuild.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/integration.pipeline.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[andrzej-stencel]

@pazone can you fix the backport conflicts?

[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 mergify/bp/8.18/pr-6972 upstream/mergify/bp/8.18/pr-6972
git merge upstream/8.18
git push upstream mergify/bp/8.18/pr-6972

[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

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: cfa9021

History

• 💔 Build #18344 failed 4d58fe5
• 💔 Build #18094 failed 4f8d91f

cc @pazone