We are trying to use the plugin to find out where pipelines failed, similar to https://github.com/jenkinsci/opentelemetry-plugin/issues/281.
To make this easier, PR https://github.com/jenkinsci/opentelemetry-plugin/pull/283 already implemented to 'Use spanStatus "unset" rather than "ko" when interruption cause is parallel fail fast'.
However, later stages that are also 'skipped due to earlier failure(s)' are still marked with otel.status_code=ERROR.
I would expect that these stages also have the spanStatus "unset"?
What feature do you want to see added?
Hi,
We are trying to use the plugin to find out where pipelines failed, similar to https://github.com/jenkinsci/opentelemetry-plugin/issues/281. To make this easier, PR https://github.com/jenkinsci/opentelemetry-plugin/pull/283 already implemented to 'Use spanStatus "unset" rather than "ko" when interruption cause is parallel fail fast'. However, later stages that are also 'skipped due to earlier failure(s)' are still marked with
otel.status_code=ERROR
. I would expect that these stages also have the spanStatus "unset"?In this example:
I would expect that
another stage
has the samespanStatus
as theparallelBranches
, instead ofotel.status_code=ERROR
:Upstream changes
No response
Are you interested in contributing this feature?
No response