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 #30795) ci: refactor pushDockerImages main pipeline #30846

Merged
merged 2 commits into from
Mar 17, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 16, 2022

This is an automatic backport of pull request #30795 done by Mergify.
Cherry-pick of de3e4cc has failed:

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

You are currently cherry-picking commit de3e4cc06d.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   Jenkinsfile

no changes added to commit (use "git add" and/or "git commit -a")

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 de3e4cc)

# Conflicts:
#	Jenkinsfile
@mergify mergify bot requested a review from a team as a code owner March 16, 2022 11:09
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Mar 16, 2022
@mergify mergify bot assigned v1v Mar 16, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 16, 2022
@botelastic
Copy link

botelastic bot commented Mar 16, 2022

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

@v1v
Copy link
Member

v1v commented Mar 16, 2022

#28286 was not backported to 7.17, so changes are a subset from the original PR

@v1v v1v removed the conflicts There is a conflict in the backported pull request label Mar 16, 2022
@elasticmachine
Copy link
Collaborator

elasticmachine commented Mar 16, 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-03-17T08:58:17.969+0000

  • Duration: 76 min 42 sec

Test stats 🧪

Test Results
Failed 0
Passed 34169
Skipped 3928
Total 38097

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

@v1v
Copy link
Member

v1v commented Mar 17, 2022

/test

@v1v v1v merged commit 6d9f9a5 into 7.17 Mar 17, 2022
@mergify mergify bot deleted the mergify/bp/7.17/pr-30795 branch March 17, 2022 11:23
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