Perhaps related, because maybe the stage view is actually only even finding the one single build and not all of them, but the Average stage times: are wrong.  They are always the same as the only stage being shown.

That tells me that this is not a display problem but a data access problem and that the stage view is showing all of the builds that it can find and it's only finding one.

But why?

This only seems to happen while a job is in progress.  Once the job completes, the older entries show up in the stage view.

We're seeing the same sort of behavior on our Jenkins. When we did some debugging, it looked like the '#' symbol is causing some confusion when passed back as part of the url to reload the view.

The team across from us change the build number from '#1234' to their svn revision '1234' and they don't see this problem.

This really is quite hideous because this is really the only alternative to Blue Ocean[1] to seeing the individual stages in pipeline jobs.

mark_h Can you expand a bit on your findings?

[1]Blue Ocean is too big, bloated and network heavy with it's constant refreshes to be effectively usable.