-
Bug
-
Resolution: Duplicate
-
Minor
-
None
There's a problem with getting an understanding of the build status in Blue Ocean when the build status changes. Developers can see that there is a yellow or red status, and that something went wrong with the build, but there is no indication as to where in the pipeline things broke (if the pipeline is not aborted with error)
Since this happens with any status change, my opinion is that its a Blue Ocean bug. The most clear and common way to reproduce is tied to the Junit Plugin, but this issue will happen with any plugin or shared library that uses currentBuild.result = 'FAILURE'
pipeline {
agent any;
// options { skipStagesAfterUnstable() }
stages {
stage("save file") {
steps {
writeFile file: "example-fail.xml", text: '''<?xml version="1.0" encoding="UTF-8" ?>
<testsuites id="20140612_170519" name="example" tests="225" failures="1262" time="0.001">
<testsuite id="codereview.cobol.analysisProvider" name="COBOL example" tests="45" failures="17" time="0.001">
<testcase id="codereview.cobol.rules.ProgramIdRule" name="an example test name" time="0.001">
<failure message="Failure in: an example test name" type="WARNING">
Bla bla bla
</failure>
</testcase>
</testsuite>
</testsuites>'''
echo "good"
}
}
stage("nothing") {
steps {
echo "good"
}
}
stage("evaluate tests") {
steps {
echo "good"
junit "example-fail.xml"
// error "forced error"
}
}
stage("still executed") {
steps {
echo "good"
}
}
}
}
- duplicates
-
-
- Resolved
-
