Skip to content

[7.17](backport #32755) action: checks for dev-tools#32798

Merged
v1v merged 1 commit into7.17from
mergify/bp/7.17/pr-32755
Aug 24, 2022
Merged

[7.17](backport #32755) action: checks for dev-tools#32798
v1v merged 1 commit into7.17from
mergify/bp/7.17/pr-32755

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Aug 24, 2022

This is an automatic backport of pull request #32755 done by Mergify.
Cherry-pick of 2515a93 has failed:

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

You are currently cherry-picking commit 2515a93e69.
  (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-dev-tools.yml
	modified:   .github/workflows/opentelemetry.yml
	modified:   Jenkinsfile.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: dev-tools/Jenkinsfile.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 2515a93)

# Conflicts:
#	dev-tools/Jenkinsfile.yml
@mergify mergify bot requested a review from a team as a code owner August 24, 2022 10:47
@mergify mergify bot requested review from faec and leehinman and removed request for a team August 24, 2022 10:47
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Aug 24, 2022
@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

💚 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-24T10:48:03.508+0000

  • Duration: 12 min 34 sec

❕ Flaky test report

No test was executed to be analysed.

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

@v1v v1v removed the conflicts There is a conflict in the backported pull request label Aug 24, 2022
@v1v v1v merged commit 0d97755 into 7.17 Aug 24, 2022
@mergify mergify bot deleted the mergify/bp/7.17/pr-32755 branch August 24, 2022 14:48
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