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 #30781) ci: split windows in mandatory and ext_win stages #30823

Merged
merged 2 commits into from
Mar 17, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 15, 2022

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

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

You are currently cherry-picking commit f0912dac8b.
  (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:
	modified:   Jenkinsfile

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   auditbeat/Jenkinsfile.yml
	both modified:   filebeat/Jenkinsfile.yml
	both modified:   heartbeat/Jenkinsfile.yml
	both modified:   metricbeat/Jenkinsfile.yml
	both modified:   packetbeat/Jenkinsfile.yml
	both modified:   winlogbeat/Jenkinsfile.yml
	both modified:   x-pack/auditbeat/Jenkinsfile.yml
	both modified:   x-pack/elastic-agent/Jenkinsfile.yml
	both modified:   x-pack/filebeat/Jenkinsfile.yml
	both modified:   x-pack/functionbeat/Jenkinsfile.yml
	both modified:   x-pack/heartbeat/Jenkinsfile.yml
	both modified:   x-pack/metricbeat/Jenkinsfile.yml
	both modified:   x-pack/osquerybeat/Jenkinsfile.yml
	both modified:   x-pack/packetbeat/Jenkinsfile.yml
	both modified:   x-pack/winlogbeat/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 f0912da)

# Conflicts:
#	auditbeat/Jenkinsfile.yml
#	filebeat/Jenkinsfile.yml
#	heartbeat/Jenkinsfile.yml
#	metricbeat/Jenkinsfile.yml
#	packetbeat/Jenkinsfile.yml
#	winlogbeat/Jenkinsfile.yml
#	x-pack/auditbeat/Jenkinsfile.yml
#	x-pack/elastic-agent/Jenkinsfile.yml
#	x-pack/filebeat/Jenkinsfile.yml
#	x-pack/functionbeat/Jenkinsfile.yml
#	x-pack/heartbeat/Jenkinsfile.yml
#	x-pack/metricbeat/Jenkinsfile.yml
#	x-pack/osquerybeat/Jenkinsfile.yml
#	x-pack/packetbeat/Jenkinsfile.yml
#	x-pack/winlogbeat/Jenkinsfile.yml
@mergify mergify bot requested review from a team as code owners March 15, 2022 08:43
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Mar 15, 2022
@mergify mergify bot assigned v1v Mar 15, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 15, 2022
@elasticmachine
Copy link
Collaborator

elasticmachine commented Mar 15, 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:02.778+0000

  • Duration: 164 min 28 sec

Test stats 🧪

Test Results
Failed 0
Passed 2757
Skipped 315
Total 3072

💚 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 15, 2022

I'll close this since 2022 is not supported

@v1v v1v closed this Mar 15, 2022
@mergify mergify bot deleted the mergify/bp/7.17/pr-30781 branch March 15, 2022 09:55
@v1v v1v restored the mergify/bp/7.17/pr-30781 branch March 16, 2022 08:57
@v1v v1v reopened this Mar 16, 2022
@v1v
Copy link
Member

v1v commented Mar 16, 2022

/test

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

v1v commented Mar 16, 2022

/test

1 similar comment
@v1v
Copy link
Member

v1v commented Mar 17, 2022

/test

@v1v v1v added automation Team:Automation Label for the Observability productivity team labels Mar 17, 2022
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Mar 17, 2022
@v1v v1v merged commit 2645bbe into 7.17 Mar 17, 2022
@mergify mergify bot deleted the mergify/bp/7.17/pr-30781 branch March 17, 2022 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation backport Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants