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.

Sign up for GitHub

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

Jump to bottom

[CI] Use new-infra-type agent targeting for chainguard build #183545

Merged
merged 1 commit into from
May 15, 2024
Merged

[CI] Use new-infra-type agent targeting for chainguard build #183545

merged 1 commit into from
May 15, 2024

Conversation

delanni
Copy link
Contributor

@delanni delanni commented May 15, 2024 •
edited by kibanamachine
Loading

Summary

This PR ties #183200 + #182582 together

@delanni delanni added Team:Operations Team label for Operations Team release_note:skip Skip the PR/issue when compiling release notes backport:all-open Backport to all branches that could still receive a release labels May 15, 2024
@delanni delanni requested a review from a team as a code owner May 15, 2024 17:01
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@delanni delanni enabled auto-merge (squash) May 15, 2024 17:26
@delanni delanni disabled auto-merge May 15, 2024 17:26
@delanni delanni merged commit 5e95a76 into elastic:main May 15, 2024
14 of 23 checks passed
@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
❌ 7.17 Backport failed because of merge conflicts

You might need to backport the following PRs to 7.17:
- chore(NA): bump node into v20 (#173461)
- Upgrade to Node.js 20 (#162696)
- [artifacts] Add CI retries (#130194)
- [artifacts] Publish (#129499)
- [artifacts] Merge docker context verification (#129399)
- [artifacts] Merge package testing with release artifacts (#129378)
❌ 8.14 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.14:
- [build] Add image based on chainguard (#183200)

Manual backport

To create the backport manually run:

node scripts/backport --pr 183545

Questions ?

Please refer to the Backport tool documentation

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 183545 locally

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Aug 24, 2024
@delanni delanni added backported backport:skip This commit does not require backporting and removed backport missing Added to PRs automatically when the are determined to be missing a backport. backport:all-open Backport to all branches that could still receive a release labels Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jbudz jbudz jbudz approved these changes

Assignees
No one assigned
Labels
backport:skip This commit does not require backporting backported release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team v8.15.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@delanni @elasticmachine @kibanamachine @kibana-ci @jbudz