-
Improvement
-
Resolution: Fixed
-
Critical
-
-
Blue Ocean 1.4 - beta 3, Blue Ocean 1.5 - beta 1
This one should almost be obvious from the description if someone has used blue ocean.
It is possible to get a run that fails very early on, but there are no reasonable flownodes, thus no steps, no stages, and useless blue ocean results screen.
In this case it should just show the full log (or the last N lines) vs failing the user.
One way to reproduce a subset of this would be to use a pipeline like the following. When clicking on a branch, it says "no steps" - this should fall back to showing the full log in the error case.
In the case where there is just one stage and in error but no steps - same applies. When there are no stages and in error - same applies. show log.
node {
def hello_message = "Hello" stage('Fake1') {
parallel firstBranch: {
sh "echo ${helo_message}" }, secondBranch: {
sh "echo ${hello_message}" }
}
}
- links to
- mentioned in
-
Page Failed to load
[JENKINS-48074] Show full log in case of no steps and no stages for a failed run
| Epic Link | New: JENKINS-35761 [ 171656 ] |
| Assignee | New: Ivan Meredith [ imeredith ] |
| Sprint | Original: Blue Ocean 1.4 - beta 4 [ 441 ] | New: Blue Ocean 1.4 - beta 3 [ 416 ] |
| Sprint | Original: Blue Ocean 1.4 - beta 3 [ 416 ] | New: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 5 [ 416, 451 ] |
| Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
| Description |
Original:
This one should almost be obvious from the description if someone has used blue ocean. It is possible to get a run that fails very early on, but there are no reasonable flownodes, thus no steps, no stages, and useless blue ocean results screen. In this case it should just show the full log (or the last N lines) vs failing the user. |
New:
This one should almost be obvious from the description if someone has used blue ocean. It is possible to get a run that fails very early on, but there are no reasonable flownodes, thus no steps, no stages, and useless blue ocean results screen. In this case it should just show the full log (or the last N lines) vs failing the user. One way to reproduce a subset of this would be to use a pipeline like the following. When clicking on a branch, it says "no steps" - this should fall back to showing the full log in the error case. In the case where there is just one stage and in error but no steps - same applies. When there are no stages and in error - same applies. show log. node \{ def hello_message = "Hello" stage('Fake1') \{ parallel firstBranch: \{ sh "echo $\{helo_message}" }, secondBranch: \{ sh "echo $\{hello_message}" } } } |
Nicolae Pascu
made changes -
| Assignee | Original: Ivan Meredith [ imeredith ] | New: Nicolae Pascu [ nicu ] |
alobato it could be good if you could add some color here, perhaps with an example if possible, or a screen shot of the worst cases as you see them?