Status: Closed (View Workflow)
Jenkins 2.7.3. Blue Ocean Built at 7th September 2016 10:13 AM
· (no branch)
I have noticed this weird anomaly with a Pipeline, when following along at home (karaoke mode I think you call it). When I hit a stage with a sh step, the step is rendered as if it is "open" (arrow pointing down), but there is no console output being emitted. The UI seems to be stuck there, and won't continue to the next stage's steps.
Interestingly enough, clicking the step "closed" and then "re-opening" it, seems to unfreeze the interface
rtyler can you please include a git repository or Jenkinsfile for us to use in reproduction?
jamesdumay, it's linked right there.
Here's a NON HYPERLINKED VERSION https://github.com/reiseburo/verspaetung/blob/master/Jenkinsfile
tscherler speaking further with Tyler about this on IRC, it appears that the Pipeline gets to this step and tries to expand it. No log is shown and the Pipeline does not continue.
If he opens then closes the expander, he then sees the log scrolling and the Pipeline continues as per normal.
I can reproduce it and from the first look, it seems that the initial answer of the rest service is an empty log, without the flag to indicate that there are more lines of log to come. Therefore we do not refetch the log. When you click on it to collapse and then again to expand, we see (onExpand) that the log is null and therefore try to refetch it again and then the server response is correct.
Will need to debug it more though and see where to fix it.
Well I could reproduce it the first time, now implementing some logs I did not saw it anymore.
I cannot reproduced anymore which makes me wonder whether there is some kind of race condition. will try with my old laptop to see how it goes.
I should note, that my Pipeline is this one and I think the fact that the first stage does not have a sh in it is part of the reproduction case.
With another Pipeline, that starts with a sh right in the first stage, that seems to start (shows a little bit of console output), but doesn't "follow" the console output as the sh step continues to emit output (it puts out a lot)