Backport PR #15539 to 7.17: [ci] JDK matrix Buildkite pipelines (part 1) #15556
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport PR #15539 to 7.17 branch, original message:
Release notes
[rn:skip]
What does this PR do?
This commit is the first part of the migration of JDK matrix tests
from Jenkins to Buildkite. There will be two separate pipelines, for
Linux and Windows, and this commit only adds the Linux one.
Linux support is currently limited to Ubuntu 22.04 and 20.04, but
additional operating systems will be added seamlessly outside of the Logstash
repository, via through additional VM images.
Pipeline steps are created dynamically and the underlying script is meant to be
common for Linux and Windows. Windows is currently a stub and
will be added in a follow up PR.
Checklist
- [ ] 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 (and/or docker env variables)How to test this PR locally
Trigger a build by clicking https://buildkite.com/elastic/logstash-linux-jdk-matrix-pipeline#new and using
pull/15539/merge
in thebranch
field.Related issues
Screenshots
When the (Linux) job gets triggered manually, it's paused prompting the user to choose:
once that's done, it runs the jobs in groups per "OS-JDK".
The steps are dynamically built and emitted for debugging/reference purposes.
We also display a markdown table per group, with the status of each individual test using annotations like: