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

Remove BK PR Bot trigger for x-pack/heartbeat #39014

Merged

Conversation

dliappis
Copy link
Contributor

@dliappis dliappis commented Apr 17, 2024

Proposed commit message

In preparation for the migration to a static
pipeline (#38845), this commit removes the
Buildkite PR Bot trigger for the pipeline.

Relates https://github.com/elastic/ingest-dev/issues/3072

In preparation for the migration to a static
pipeline (elastic#38845), this commit removes the
Buildkite PR Bot trigger for the pipeline.
@dliappis dliappis self-assigned this Apr 17, 2024
@dliappis dliappis requested a review from a team as a code owner April 17, 2024 14:33
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Apr 17, 2024
@dliappis dliappis requested a review from alexsapran April 17, 2024 14:33
@dliappis dliappis added the ci label Apr 17, 2024
Copy link
Contributor

mergify bot commented Apr 17, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @dliappis? 🙏.
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

@dliappis dliappis enabled auto-merge (squash) April 17, 2024 14:40
@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: 14 min 15 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!)

@dliappis dliappis merged commit 4a5d333 into elastic:main Apr 17, 2024
12 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants