We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, if a Cobertura check fails, the whole job becomes unstable and all stages (in the Blue Ocean view) are marked with yellow colour. With multiple stages, it is difficult to find the reason for instability. There is a new API that could be used to do so: https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/
It is possible to implement such a solution?
The text was updated successfully, but these errors were encountered:
According to the post, we need to upgrade our baseline Jenkins version to 2.138.4(now it is 2.60.3). What do you think about this change? @jeffpearce
Sorry, something went wrong.
No branches or pull requests
Currently, if a Cobertura check fails, the whole job becomes unstable and all stages (in the Blue Ocean view) are marked with yellow colour. With multiple stages, it is difficult to find the reason for instability. There is a new API that could be used to do so:
https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/
It is possible to implement such a solution?
The text was updated successfully, but these errors were encountered: