-
Improvement
-
Resolution: Cannot Reproduce
-
Minor
-
-
Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2
Whether this is a rendering issue in Blue Ocean or an issue with pipeline-github is unclear, but the URL is: /blue/organizations/jenkins/pipeline-github%2Fcore/detail/PR-88/1/pipeline/1051
Every node in the graph is a green checkmark, making me think they are passing.
The top header is red, making me think that it failed, but it doesn't say anything on the screen to indicate why it is considered a failure. This information should probably be in a prominent location, but because it isn't, I have to assume it's a bug.
There is a similar-sounding report in JENKINS-32146 but I'm not entirely sure it's the same.
[JENKINS-47365] Overall pipeline build is a failure even though all stages are green, and reason for failure is mentioned nowhere
trejkaz
created issue -
| Assignee | New: James Dumay [ jamesdumay ] |
| Sprint | New: Blue Ocean 1.4 - beta 1 [ 401 ] |
| Sprint | Original: Blue Ocean 1.4 - beta 1 [ 401 ] | New: Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2 [ 401, 426 ] |
trejkaz
added a comment - I'm doing my best, but now I hit that other frequent bug where the /pr/ URL never loads, so I can't get back to the build which generated that result.
trejkaz
added a comment - I'm doing my best, but now I hit that other frequent bug where the /pr/ URL never loads, so I can't get back to the build which generated that result.
trejkaz
added a comment - Spun off JENKINS-47492 for the issue with the blue ocean listing page and meanwhile will wait until the next time I see it happen and then post logs for that one.
trejkaz
added a comment - Spun off JENKINS-47492 for the issue with the blue ocean listing page and meanwhile will wait until the next time I see it happen and then post logs for that one. trejkaz
added a comment - The other issue temporarily stopped happening but for some reason Jenkins has deleted the build which originally had the problem, so now I definitely have to wait to find some other build doing it.
trejkaz
added a comment - The other issue temporarily stopped happening but for some reason Jenkins has deleted the build which originally had the problem, so now I definitely have to wait to find some other build doing it. | Sprint | Original: Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2 [ 401, 426 ] | New: Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 [ 401, 416, 426 ] |
Testing Notes:
- If implemented, automated tests (at the unit level is fine) should be included to verify that overall run status is appropriate to the build and test results for that run
- UI tests could be provided as well, to check for consistent, useful messaging for failed builds. Many of the existing UI tests are happy-path in nature, and testing for correct function during failed builds would be a welcome addition.
trejkaz could you please share your build log and Jenkinsfile? Its impossible for us to know what is going on without that info.
If you wish, you can share directly with me by emailing them to me at jdumay@cloudbees.com