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

[8.13](backport #38926) Moved winlogbeat pipeline to central pipeline #39069

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 19, 2024

Proposed commit message

In scope of https://github.com/elastic/ingest-dev/issues/3072 - moved winlogbeatt pipeline triggering to central pipeline
BK Builds: https://buildkite.com/elastic/beats-winlogbeat/builds?branch=elastic%3Amergify%2Fbp%2F8.13%2Fpr-38926

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 #38926 done by [Mergify](https://mergify.com).

@mergify mergify bot requested a review from a team as a code owner April 19, 2024 07:06
@mergify mergify bot added the backport label Apr 19, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 19, 2024
@elasticmachine
Copy link
Collaborator

elasticmachine commented Apr 19, 2024

💚 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: 16 min 43 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!)

@oakrizan oakrizan force-pushed the mergify/bp/8.13/pr-38926 branch from c160cb6 to 69a6e4c Compare April 19, 2024 09:44
@oakrizan oakrizan added Team:Elastic-Agent Label for the Agent team and removed needs_team Indicates that the issue/PR needs a Team:* label labels Apr 19, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

Copy link
Contributor Author

mergify bot commented Apr 22, 2024

This pull request has not been merged yet. Could you please review and merge it @oakrizan? 🙏

@oakrizan oakrizan force-pushed the mergify/bp/8.13/pr-38926 branch from 69a6e4c to 60df06a Compare April 22, 2024 07:14
Copy link
Contributor Author

mergify bot commented Apr 22, 2024

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.13/pr-38926 upstream/mergify/bp/8.13/pr-38926
git merge upstream/8.13
git push upstream mergify/bp/8.13/pr-38926

* updated common.sh

* updated cnetral pipleine with winlogbeat

* fixed typo

(cherry picked from commit 2250273)
@oakrizan oakrizan force-pushed the mergify/bp/8.13/pr-38926 branch from 60df06a to 4f202b2 Compare April 22, 2024 09:03
Copy link
Contributor

@dliappis dliappis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@oakrizan oakrizan merged commit 4c40b5c into 8.13 Apr 22, 2024
121 of 125 checks passed
@oakrizan oakrizan deleted the mergify/bp/8.13/pr-38926 branch April 22, 2024 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants