[ci] Support soft failures #169244
Labels
Team:Operations
Team label for Operations Team
Comments
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
We had an intent for this in this PR, but we kind of got stuck: https://github.com/elastic/kibana-buildkite-build-bot/pull/3 |
jbudz
added a commit
that referenced
this issue
Oct 23, 2023
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-suites` and `ci:cypress-burn` labels. I'm open to all improvements here, not sure this quite finds the right balance between stability and noise.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Soft failures allow step failures to not fail the entire build - https://buildkite.com/docs/pipelines/command-step
While these can be enabled in buildkite, our pull request comments still indicate a build failure causing confusion on whether a pull request is merge-able.
The text was updated successfully, but these errors were encountered: