Conversation
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
| @@ -0,0 +1,44 @@ | |||
| projects: | |||
There was a problem hiding this comment.
What beats are onboarded to this automated pipeline generator.
These are folders from the top of the project. They should also host a similar buildkite.yml file.
| # - GitHub label <sub-stage-name> . i.e: integTest or unitTest-arm or unitTest-macos ... | ||
| extended: | ||
| # NOTE: stage name should be unique! | ||
| integTest: |
There was a problem hiding this comment.
This step can be forced to run using:
- The GitHub comment
/test auditbeat integTest - The GitHub label
auditbeat-integTest
| integTest: | ||
| command: "mage build integTest" | ||
| platform: "core-ubuntu-2004-aarch64" | ||
| integTest-arm: |
There was a problem hiding this comment.
This step can be forced to run using:
- The GitHub comment
/test auditbeat integTest-arm - The GitHub label
auditbeat-integTest-arm
| # - on PRs if: | ||
| # - GitHub comment /test auditbeat <sub-stage-name> . i.e: /test auditbeat integTest | ||
| # - GitHub label <sub-stage-name> . i.e: integTest or unitTest-arm or unitTest-macos ... | ||
| extended: |
There was a problem hiding this comment.
All the stages in the extended meta-stage will be triggered for PRs using:
- The GitHub comment
/test auditbeat-extended - The GitHub label
extended-auditbeat
|
If I understand correctly it allows us to keep the previously created |
|
buildkite test auditbeat |
.buildkite/pipeline.py
Outdated
|
|
||
| def create_entity(self): | ||
| data = """ | ||
| {% if group.steps|length > 0 %} |
There was a problem hiding this comment.
Can we switch from templating the YAML to just doing something along the lines of
import yaml
# ...
yaml.dumps(self)There was a problem hiding this comment.
Sure, it was just a quick PoC to illustrate how this could work. Moving from one implementation to another is totally fine and makes sense if that's the way to move this forward :)
fefe766 to
d006b37
Compare
|
Added:
I think we can merge this PR. Further improvements:
|
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
This commit introduces a main pipeline generator similar to the one used with Jenkins #20104 to help with the migration to Buildkite. Co-authored-by: Pavel Zorin <pavel.zorin@elastic.co> Co-authored-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 4b7467b) # Conflicts: # .buildkite/hooks/pre-command
This commit introduces a main pipeline generator similar to the one used with Jenkins #20104 to help with the migration to Buildkite. Co-authored-by: Pavel Zorin <pavel.zorin@elastic.co> Co-authored-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 4b7467b) # Conflicts: # .buildkite/hooks/pre-command Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
This commit introduces a main pipeline generator similar to the one used with Jenkins #20104 to help with the migration to Buildkite. Co-authored-by: Pavel Zorin <pavel.zorin@elastic.co> Co-authored-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 4b7467b) Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
This commit introduces a main pipeline generator similar to the one used with Jenkins #20104 to help with the migration to Buildkite. Co-authored-by: Pavel Zorin <pavel.zorin@elastic.co> Co-authored-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 4b7467b) Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
Proposed commit message
Tasks
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs