Skip to content
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

[7.17](backport #38162) PoC: use pipeline generator #38485

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 20, 2024

Proposed commit message

Tasks

  • Enable when conditions.
    • GitHub comment - for individual stages and groups
    • GitHub labels - for individual stages
    • Changeset
    • 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


This is an automatic backport of pull request #38162 done by [Mergify](https://mergify.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)
@mergify mergify bot requested review from a team as code owners March 20, 2024 15:20
@mergify mergify bot added the backport label Mar 20, 2024
@mergify mergify bot requested review from fearful-symmetry and faec and removed request for a team March 20, 2024 15:20
@mergify mergify bot assigned v1v Mar 20, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 20, 2024
@botelastic
Copy link

botelastic bot commented Mar 20, 2024

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 56 min 5 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 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!)

@alexsapran alexsapran merged commit a0a0191 into 7.17 Mar 22, 2024
29 of 30 checks passed
@alexsapran alexsapran deleted the mergify/bp/7.17/pr-38162 branch March 22, 2024 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants