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

[ci] Don't start APM/Profiling cypress if pre-checks don't pass #208569

Merged
merged 1 commit into from
Jan 28, 2025

Conversation

delanni
Copy link
Contributor

@delanni delanni commented Jan 28, 2025

Summary

https://buildkite.com/elastic/kibana-on-merge/builds/60136 shows how even though some preliminary checks failed, some cypress tests started after the build step was successful. It's probably because they had explicit dependencies, but only on a subset of the pre-checks.

@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 Jan 28, 2025
@delanni delanni requested a review from a team as a code owner January 28, 2025 16:18
@elasticmachine
Copy link
Contributor

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

@delanni delanni merged commit 90d768b into main Jan 28, 2025
14 of 15 checks passed
@delanni delanni deleted the on-merge-fix-task-dependencies branch January 28, 2025 17:19
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 7.17, 8.16, 8.17, 8.x

https://github.com/elastic/kibana/actions/runs/13015939470

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jan 28, 2025
…tic#208569)

## Summary
https://buildkite.com/elastic/kibana-on-merge/builds/60136 shows how
even though some preliminary checks failed, some cypress tests started
after the build step was successful. It's probably because they had
explicit dependencies, but only on a subset of the pre-checks.

(cherry picked from commit 90d768b)
@kibanamachine
Copy link
Contributor

💔 Some backports could not be created

Status Branch Result
7.17 Backport failed because of merge conflicts
8.16 Backport failed because of merge conflicts
8.17 Backport failed because of merge conflicts
8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 208569

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Jan 28, 2025
…x27;t pass (#208569) (#208585)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[ci] Don't start APM/Profiling cypress if pre-checks don't
pass (#208569)](#208569)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Alex
Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-01-28T17:19:52Z","message":"[ci]
Don't start APM/Profiling cypress if pre-checks don't pass
(#208569)\n\n##
Summary\nhttps://buildkite.com/elastic/kibana-on-merge/builds/60136
shows how\neven though some preliminary checks failed, some cypress
tests started\nafter the build step was successful. It's probably
because they had\nexplicit dependencies, but only on a subset of the
pre-checks.","sha":"90d768be9b35ac26a3b938edac5c1af47cab980a","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","v9.0.0","backport:all-open"],"title":"[ci]
Don't start APM/Profiling cypress if pre-checks don't
pass","number":208569,"url":"https://github.com/elastic/kibana/pull/208569","mergeCommit":{"message":"[ci]
Don't start APM/Profiling cypress if pre-checks don't pass
(#208569)\n\n##
Summary\nhttps://buildkite.com/elastic/kibana-on-merge/builds/60136
shows how\neven though some preliminary checks failed, some cypress
tests started\nafter the build step was successful. It's probably
because they had\nexplicit dependencies, but only on a subset of the
pre-checks.","sha":"90d768be9b35ac26a3b938edac5c1af47cab980a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208569","number":208569,"mergeCommit":{"message":"[ci]
Don't start APM/Profiling cypress if pre-checks don't pass
(#208569)\n\n##
Summary\nhttps://buildkite.com/elastic/kibana-on-merge/builds/60136
shows how\neven though some preliminary checks failed, some cypress
tests started\nafter the build step was successful. It's probably
because they had\nexplicit dependencies, but only on a subset of the
pre-checks.","sha":"90d768be9b35ac26a3b938edac5c1af47cab980a"}}]}]
BACKPORT-->

Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:all-open Backport to all branches that could still receive a release release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team v8.18.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants