Skip to content

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

Merged
pazone merged 3 commits into8.17from
mergify/bp/8.17/pr-6972
Mar 7, 2025
Merged

[8.17](backport #6972) [CI] Fixed container images packaging#7194
pazone merged 3 commits into8.17from
mergify/bp/8.17/pr-6972

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Mar 5, 2025

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).

* [CI] Fixed container images packaging

* Packaging Ubuntu matrix

* Improve matrix representation

* Removed matrix packaging if favour to unique step keys

* Cleanup

* Added binfmt

* Pinned binfmt to v8.1.5

* Correct step names

* Changed packaging ARM machine type

* pinned qemu-v9.2.0-51

* Remove qemu

* Removed deb and rpm integration packaging

* Reordered packaging steps

* [CI] Build FIPS ARM Linux on ARM machine. Added missing retries

* Fixed FIPS

* [CI] Corrected integration tests packaging dependencies

* [CI] single buildkite download invocation

* Added missing retries

(cherry picked from commit 14943f0)

# Conflicts:
#	.buildkite/integration.pipeline.yml
@mergify mergify bot requested review from a team as code owners March 5, 2025 10:57
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Mar 5, 2025
@mergify mergify bot requested review from pchila and swiatekm and removed request for a team March 5, 2025 10:57
@mergify mergify bot assigned pazone Mar 5, 2025
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Mar 5, 2025

Cherry-pick of 14943f0 has failed:

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

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

@elastic-sonarqube
Copy link
Copy Markdown

Quality Gate passed 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

@pazone pazone removed the conflicts There is a conflict in the backported pull request label Mar 7, 2025
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Mar 7, 2025

💔 Build Failed

Failed CI Steps

History

cc @pazone

@pazone pazone merged commit 4773f09 into 8.17 Mar 7, 2025
12 checks passed
@pazone pazone deleted the mergify/bp/8.17/pr-6972 branch March 7, 2025 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants