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

Bump elastic stack version automation (backport #25148) #25282

Merged
merged 1 commit into from
Apr 26, 2021

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 23, 2021

This is an automatic backport of pull request #25148 done by Mergify.

Cherry-pick of cc29196 has failed:

On branch mergify/bp/7.x/pr-25148
Your branch is up to date with 'origin/7.x'.

You are currently cherry-picking commit cc29196dfb.
  (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:   .ci/bump-stack-version.sh
	modified:   .gitignore

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   .mergify.yml

To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/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.io/

(cherry picked from commit cc29196)

# Conflicts:
#	.mergify.yml
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Apr 23, 2021
@mergify mergify bot assigned v1v Apr 23, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 23, 2021
@elasticmachine
Copy link
Collaborator

💚 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

Expand to view the summary

Build stats

  • Build Cause: Pull request #25282 opened

  • Start Time: 2021-04-23T16:13:46.565+0000

  • Duration: 17 min 12 sec

  • Commit: 58b8815

Trends 🧪

Image of Build Times

❕ Flaky test report

No test was executed to be analysed.

@v1v v1v merged commit 2df45c7 into 7.x Apr 26, 2021
@mergify mergify bot deleted the mergify/bp/7.x/pr-25148 branch April 26, 2021 10:38
@v1v v1v added automation Team:Automation Label for the Observability productivity team and removed needs_team Indicates that the issue/PR needs a Team:* label labels Apr 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation backport conflicts There is a conflict in the backported pull request Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants