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 #39869) Migrate github checks to buildkite for libbeat and x-pack/libbeat #39877

Merged
merged 3 commits into from
Jun 13, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jun 12, 2024

Proposed commit message

Migrate github checks to buildkite for libbeat and x-pack/libbeat

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.

Related issues

Logs


This is an automatic backport of pull request #39869 done by [Mergify](https://mergify.com).

…9869)

* Update

* Update pipeline.xpack.libbeat.yml

* Update pipeline.xpack.libbeat.yml

* update

(cherry picked from commit 02a57f7)

# Conflicts:
#	.buildkite/libbeat/pipeline.libbeat.yml
#	.github/workflows/check-libbeat.yml
@mergify mergify bot requested a review from a team as a code owner June 12, 2024 13:15
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Jun 12, 2024
Copy link
Contributor Author

mergify bot commented Jun 12, 2024

Cherry-pick of 02a57f7 has failed:

On branch mergify/bp/7.17/pr-39869
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit 02a57f7648.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/x-pack/pipeline.xpack.libbeat.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   .buildkite/libbeat/pipeline.libbeat.yml
	deleted by them: .github/workflows/check-libbeat.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 12, 2024
@botelastic
Copy link

botelastic bot commented Jun 12, 2024

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

@ev1yehor ev1yehor requested a review from a team as a code owner June 12, 2024 22:04
@ev1yehor ev1yehor requested review from fearful-symmetry and faec and removed request for a team June 12, 2024 22:04
@ev1yehor ev1yehor removed the conflicts There is a conflict in the backported pull request label Jun 13, 2024
@ev1yehor ev1yehor merged commit 18d2057 into 7.17 Jun 13, 2024
21 checks passed
@ev1yehor ev1yehor deleted the mergify/bp/7.17/pr-39869 branch June 13, 2024 13:14
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.

2 participants