-
Notifications
You must be signed in to change notification settings - Fork 213
[9.0] (backport #9048) ci: build agent from snapshot DRA #9281
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
Conversation
|
Cherry-pick of a155660 has failed: 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 |
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
first I wanna see how this PR behaves on |
|
ok CI run on main is green and the automation PR looks correct #9283 proceeding with addressing the conflicts |
0fc66a5 to
6818837
Compare
* Redefine ExpectedBinaries as YAML config * Move ExpectedBinaries closer to package spec file * Fix error formatting in downloadDRAArtifacts * add packageName template to ExpectedPackages * use a relaxed dependencies version for IAR releases * Remove FIPS hack introduced in PR #7486 * Allow for a looser match on relaxing dependencies versions * Add debug logging when packaging with EXTERNAL=true * move package tests to dedicated package
* Add component list to specs * extract component dependencies from the packages to be built * Refactor component extraction from package specs * Fix package tests error handling * Inject dependencies and remove references to ExpectedBinaries * Remove ExpectedBinaries global * Add rootdir to components * Extract actual version matched on the package file and use it to render RootDir * Package elastic-agent FIPS specs when FIPS=true is specified * refactor ResolveManifestPackage * Move FIPS compile settings in packages.yml * Add more FIPS components * Properly handle dependenciesVersion when calling mage package * Refactor ChecksumsWithoutManifest to use list of dependencies instead of globbing files * Rework useDRAAgentBinaryForPackage for repackaging agent Define elastic-agent-core components (both FIPS and non-FIPS variants) and define package name and root dir templates. Implement some filtering on component list to extract the correct component definition according to the FIPSBuild flag. Refactor code that downloads pre-compiled elastic-agent binaries and places them in the golangCrossBuild directory to make use of the new component definition. * Write spec FIPS flag into manifest.yaml when packaging * Add FIPS elastic agent basic and cloud docker images * Build FIPS docker images in CI packaging * Fix FIPS .tar.gz package tests * Restructure package tests * Extend FIPS check to all binaries in components directory * Create FIPS elastic-agent-core artifacts in elastic-agent-binary-dra pipeline * Cleanup ChecksumsWithManifest and improve godoc * Improve godoc for BinarySpec
Restore qualifier for elastic-agent-core packaging specs to avoid changing the rootDir name of the archives. The qualifier had been removed in PR #7690 trying to use the spec name: this worked to get the desired file name but changed the root Dir name which uses '{{.BeatName}}{{if .Qualifier}}-{{.Qualifier}}{{end}}' in the template definition instead of '{{.Name}}' which would render the spec name.
* feat: rework .package-version and mage integration:UpdatePackageVersion to make CI build always from snapshot DRA * feat: incorporate USE_PACKAGE_VERSION in mage * experiment: bump version.go * Revert "experiment: bump version.go" This reverts commit a57ee10. * chore: bump .package-version * feat: allow AGENT_VERSION to be overridden by env var * fix: use named args for all args in integration_tests_tf.ps1 * feat: panic on err of initPackageVersion * fix: don't panic when .package-version file doesn't exist, log it instead * feat: rework fabrication of CI_ELASTIC_AGENT_DOCKER_IMAGE * feat: use os.WriteFile in writePackageVersion * chore: bump to latest snapshot DRA * fix: always DownloadManifest if PackagingFromManifest is set in mage package * fix: check err of filepath.Abs(dropPath)
6ff5311 to
b1d731f
Compare
2133791 to
e98e93f
Compare
|
💚 Build Succeeded
History
|
pchila
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nitpick on FIPS settings struct, not blocking and can be fixed in a follow-up PR.
Package DRA build looks good.
Thank you for the backport!





What does this PR do?
This PR reworks the
.package-versionfile format and integrates it into our CI and mage workflows to enable deterministic, snapshot-based builds of Elastic Agent based on published DRA (Downloadable Release Artifacts).Key changes:
.package-versionis now a structured JSON file containing version metadata (version,build_id,stack_build_id,manifest_url, etc.)..package-versionwhenUSE_PACKAGE_VERSION=trueis set.magetargetUpdatePackageVersionreplaces previous logic with a structured update mechanism for.package-version..package-version.Why is it important?
We previously had a fundamental dependency issue in the release flow: to produce a new Elastic Agent DRA, we needed to bump the agent version — but our CI integration tests required that same DRA to already exist in order to pass. This created a timing problem and made the release workflow fragile.
With this PR:
.package-versionwhenUSE_PACKAGE_VERSION=trueis set, allowing packaging and testing to rely on a known-good, previously published DRA..package-version, now become the authoritative source of truth for the Elastic Agent version used in the repo and must be handled with utmost care..package-versionhas been merged.This enables a reproducible and version-pinned CI system while allowing us to automate snapshot bumps in a controlled and testable way.
An experimental version bump under commit
a57ee10verified this flow successfully. The CI run is available here.Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
None expected. Existing workflows are unaffected unless
USE_PACKAGE_VERSION=trueis explicitly set. In that case,.package-versionis required and must be up to date.How to test this PR locally
specify
USE_PACKAGE_VERION=trueand call anymagetarget e.g.Related issues
This is an automatic backport of pull request #9048 done by [Mergify](https://mergify.com).