Skip to content

[8.4](backport #32750) action: checks for winlogbeat and x-pack/winlogbeat#32803

Merged
v1v merged 5 commits into8.4from
mergify/bp/8.4/pr-32750
Aug 25, 2022
Merged

[8.4](backport #32750) action: checks for winlogbeat and x-pack/winlogbeat#32803
v1v merged 5 commits into8.4from
mergify/bp/8.4/pr-32750

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Aug 24, 2022

This is an automatic backport of pull request #32750 done by Mergify.
Cherry-pick of 4f80e0f has failed:

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

You are currently cherry-picking commit 4f80e0f96a.
  (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:
	new file:   .github/workflows/check-winlogbeat.yml
	new file:   .github/workflows/check-xpack-winlogbeat.yml
	modified:   winlogbeat/Jenkinsfile.yml
	modified:   x-pack/winlogbeat/Jenkinsfile.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/opentelemetry.yml

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


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

(cherry picked from commit 4f80e0f)

# Conflicts:
#	.github/workflows/opentelemetry.yml
@mergify mergify bot requested review from a team as code owners August 24, 2022 11:27
@mergify mergify bot removed the request for review from a team August 24, 2022 11:27
@mergify mergify bot added the backport label Aug 24, 2022
@mergify mergify bot requested a review from belimawr August 24, 2022 11:27
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Aug 24, 2022
@mergify mergify bot requested a review from rdner August 24, 2022 11:27
@mergify mergify bot assigned v1v Aug 24, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 24, 2022
@botelastic
Copy link

botelastic bot commented Aug 24, 2022

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

@elasticmachine
Copy link
Contributor

elasticmachine commented Aug 24, 2022

💚 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

  • Start Time: 2022-08-24T14:51:43.741+0000

  • Duration: 37 min 13 sec

Test stats 🧪

Test Results
Failed 0
Passed 927
Skipped 9
Total 936

💚 Flaky test report

Tests succeeded.

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

@mergify
Copy link
Contributor Author

mergify bot commented Aug 24, 2022

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.4/pr-32750 upstream/mergify/bp/8.4/pr-32750
git merge upstream/8.4
git push upstream mergify/bp/8.4/pr-32750

@mergify
Copy link
Contributor Author

mergify bot commented Aug 25, 2022

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.4/pr-32750 upstream/mergify/bp/8.4/pr-32750
git merge upstream/8.4
git push upstream mergify/bp/8.4/pr-32750

@v1v v1v merged commit b407e44 into 8.4 Aug 25, 2022
@mergify mergify bot deleted the mergify/bp/8.4/pr-32750 branch August 25, 2022 09:42
@elasticmachine
Copy link
Contributor

💚 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

  • Start Time: 2022-08-25T09:12:27.078+0000

  • Duration: 36 min 21 sec

Test stats 🧪

Test Results
Failed 0
Passed 927
Skipped 9
Total 936

💚 Flaky test report

Tests succeeded.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport conflicts There is a conflict in the backported pull request 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