[ci] Move cypress burn tests out of base pull request pipeline#169326
Merged
jbudz merged 2 commits intoelastic:mainfrom Oct 23, 2023
Merged
[ci] Move cypress burn tests out of base pull request pipeline#169326jbudz merged 2 commits intoelastic:mainfrom
jbudz merged 2 commits intoelastic:mainfrom
Conversation
Contributor
|
Pinging @elastic/kibana-operations (Team:Operations) |
Contributor
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Ikuni17
approved these changes
Oct 23, 2023
patrykkopycinski
approved these changes
Oct 23, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently operations does not have a good mechanism for communicating soft failures, leading to confusion on pull requests. We're tracking support for soft failures at #169244.
For example, in #169309, it doesn't makes sense for the author to be responsible for fixing flakiness here, so we need to make it clear it can be ignored or find a way to skip this step in similar situations.
This moves the cypress burn out of the base pull request pipeline, behind the
ci:all-cypress-suitesandci:cypress-burnlabels. I'm open to all improvements here, not sure this quite finds the right balance between stability and noise.