Jenkins provides more detailed step/stage results than OTEL's Ok/Error/Unset, such as "Not Executed", "Unstable", and more. These statuses are also what Jenkins users are accustomed to seeing in the Jenkins classic/Blue Ocean UIs. Similar information is already provided at a build level (ci.pipeline.run.result).
I propose adding a jenkins.pipeline.step.result attribute to step and stage spans with this information.
What feature do you want to see added?
Jenkins provides more detailed step/stage results than OTEL's Ok/Error/Unset, such as "Not Executed", "Unstable", and more. These statuses are also what Jenkins users are accustomed to seeing in the Jenkins classic/Blue Ocean UIs. Similar information is already provided at a build level (
ci.pipeline.run.result
).I propose adding a
jenkins.pipeline.step.result
attribute to step and stage spans with this information.Upstream changes
No response