ci: Daily Releasable Artifacts pipeline#7530
Conversation
|
This pull request does not have a backport label. Could you fix it @v1v? 🙏
NOTE: |
it generates all the required artifacts
…er into feature/dra-second-approach * 'feature/dra-second-approach' of github.com:v1v/apm-server: Update .ci/packaging.groovy Update .ci/packaging.groovy Update .ci/packaging.groovy
…approach * upstream/main: jjbb: Daily Releasable Artifacts pipeline (elastic#7531) [Automation] Update elastic stack version to 8.2.0-ff67d7b8 for testing (elastic#7561) Update to elastic/beats@b9d17e0c161b (elastic#7560) systemtest: set min TLS version to 1.2 (elastic#7551) Update module deps (elastic#7552) [Automation] Update elastic stack version to 8.2.0-9bac538c for testing (elastic#7549) Update to elastic/beats@ab30a0234e1c (elastic#7546) [automation] update libbeat and beats packaging (elastic#7534) Fix modelindexer benchmarks (elastic#7533) [Automation] Update elastic stack version to 8.2.0-fee3b8d2 for testing (elastic#7537) Removed `observer.version_major` (elastic#7399) [Docs - OpenTelemetry] Document limitation on OTLP/HTTP not being supported (elastic#7505)
…is not available earlier
This reverts commit e461a46.
|
|
||
| export PLATFORMS='linux/amd64' | ||
| # linux/amd64 is in the default list already | ||
| export PLATFORMS="${PLATFORMS:-+linux/amd64}" |
There was a problem hiding this comment.
IIRC PLATFORMS="+linux/amd64" will build the defaults platform plus linux/amd64, if you set PLATFORMS='linux/amd64' it build only linux/amd64
There was a problem hiding this comment.
I dunno which behaviour we want here
There was a problem hiding this comment.
In fact, I don't need this anymore, it was wrongly copied from another PR that I worked with
Co-authored-by: Ivan Fernandez Calvo <kuisathaverat@users.noreply.github.com>
axw
left a comment
There was a problem hiding this comment.
This looks great, thank you.
Are you going to remove the Package stage from the top-level pipeline?
| unstash 'source' | ||
| dir("${BASE_DIR}"){ | ||
| withMageEnv() { | ||
| sh(label: 'make release-manager-snapshot', script: 'make release-manager-snapshot') |
There was a problem hiding this comment.
I just realised we're only ever building/publishing snapshot images. We'll need to also build staging images for release branches.
There was a problem hiding this comment.
I somehow missed this particular bit, we can iterate on this after merging this PR, what do you think?
Co-authored-by: Andrew Wilkins <axwalk@gmail.com>
The main pipeline runs the package on-demand too:
I'm inclined to keep it for now, since this new pipeline will only work for the main/x.y branches |
Co-authored-by: Mike Place <mike.place@elastic.co>
(cherry picked from commit 687f632)
(cherry picked from commit 687f632)
(cherry picked from commit 687f632)
Motivation/summary
Daily Releasable Artifacts pipeline for APM Server only on branches
Issues
Superseedes #7529
Requires #7531
Further details
This new pipeline will be triggered automatically after a build in the CI for the active branches has finished successfully.
release-managerFor clarity, it won't run on a PR basis, though it's possible to manually kick off a build in -> here I enabled the support for manual builds for PRs to help with this implementation, potentially to be removed, if so, then https://github.com/elastic/apm-server/blob/main/.ci/jobs/apm-server-package-mbp.yml#L17 should be changed to exclude
PR-*Test
I ran a few iterations within this PR to be able to validate it works as expected:
release-managersuccessfully. (I wanted to confirm theDRAstaged worked). https://artifacts-snapshot.elastic.co/apm-server/8.2.0-7c2a7da4/summary-8.2.0-SNAPSHOT.html was generatedIf it works then I'll revert e461a46 and ask for the review