beats PoC: use pipeline generator

Proposed commit message

WHAT: pipeline migration from Jenkins to Buildkite using a pipeline generator based on Python.
WHY: takes the concepts from https://github.com/elastic/beats/pull/20104 but for Buildkite

Tasks

[ ] Enable when conditions.
- [x] GitHub comment - for individual stages and groups
- [x] GitHub labels - for individual stages
- [ ] Changeset
- [x] Branches
[ ] Use catalog to generate the pipeline itself, rather than calling a python script on a pipeline.yaml file.
[ ] Support draft PRs.

Checklist

[ ] 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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

[ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

Mar 04 '24 08:03 v1v

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @v1v? 🙏. For such, you'll need to label your PR with:

The upcoming major version of the Elastic Stack
The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed branches, such as:

backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

Mar 04 '24 08:03 mergify[bot]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Duration: 79 min 25 sec

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.
/package : Generate the packages and run the E2E tests.
/beats-tester : Run the installation tests with beats-tester.
run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Mar 04 '24 09:03 elasticmachine

If I understand correctly it allows us to keep the previously created Jenkinsfile.yml-based approach without any significant structural changes. Let's figure out what else we need to do to make it work e.g. secrets management, hooks, conditional tools installation, etc.

Mar 04 '24 12:03 pazone

buildkite test auditbeat

Mar 04 '24 15:03 v1v

Added:

changeset functionality,
aws and orka support,
applied beats images for jobs. The pipeline generation is tested on filebeat and auditbeat. It works fine but I'm facing issues with filebeat crosscompile. It's not related to the pipeline generation logic.

I think we can merge this PR.

Further improvements:

change pipeline generation for comments (now it doesn't work properly)
unit tests for the pipeline.py

Mar 15 '24 00:03 pazone

:green_heart: Build Succeeded

Buildkite Build
Commit: ca2c8fc9564d6a3d66468d34fe97922e46025d16