[JIRA] (JENKINS-58604) Full Stage View only showing one

Issue Type:	Bug
Assignee:	Sam Van Oort
Attachments:	image-2019-07-22-13-20-32-346.png
Components:	pipeline-stage-view-plugin
Created:	2019-07-22 17:21
Environment:	Jenkins ver. 2.176.1
Priority:	Major
Reporter:	Brian J Murrell

The "Full Stage View" view only seems to ever be showing the currently building job any more:

There was a time when I recall seeing lots of previous jobs, but not any more it seems.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

brian.murrell@intel.com (JIRA)

unread,

Jul 31, 2019, 8:51:02 AM7/31/19

to jenkinsc...@googlegroups.com

Brian J Murrell commented on

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?

brian.murrell@intel.com (JIRA)

unread,

Aug 1, 2019, 10:44:02 AM8/1/19

to jenkinsc...@googlegroups.com

Brian J Murrell commented on

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

mark.hermon@fisglobal.com (JIRA)

unread,

Aug 14, 2019, 9:45:02 PM8/14/19

to jenkinsc...@googlegroups.com

Mark Hermon commented on

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.

brian.murrell@intel.com (JIRA)

unread,

Sep 13, 2019, 9:11:03 AM9/13/19

to jenkinsc...@googlegroups.com

Brian J Murrell assigned an issue to Sam Van Oort

Jenkins /

Change By:	Brian J Murrell
Assignee:	Brian J Murrell Sam Van Oort

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

brian.murrell@intel.com (JIRA)

unread,

Sep 13, 2019, 9:11:03 AM9/13/19

to jenkinsc...@googlegroups.com

Brian J Murrell assigned an issue to Brian J Murrell

Jenkins /

Change By:	Brian J Murrell

Assignee:	Sam Van Oort Brian J Murrell

brian.murrell@intel.com (JIRA)

unread,

Sep 13, 2019, 9:15:02 AM9/13/19

to jenkinsc...@googlegroups.com

Brian J Murrell commented on

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 Hermon 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.

mark.hermon@fisglobal.com (JIRA)

unread,

Sep 17, 2019, 6:06:02 PM9/17/19

to jenkinsc...@googlegroups.com

Mark Hermon updated an issue

Jenkins /

Change By:	Mark Hermon
Attachment:	Run 593.png

mark.hermon@fisglobal.com (JIRA)

unread,

Sep 17, 2019, 6:06:02 PM9/17/19

to jenkinsc...@googlegroups.com

Mark Hermon updated an issue

Jenkins /

Change By:	Mark Hermon
Attachment:	Run 592.png

mark.hermon@fisglobal.com (JIRA)

unread,

Sep 17, 2019, 6:06:04 PM9/17/19

to jenkinsc...@googlegroups.com

Mark Hermon updated an issue

Jenkins /

Change By:	Mark Hermon
Attachment:	Function.png

mark.hermon@fisglobal.com (JIRA)

unread,

Sep 17, 2019, 6:07:02 PM9/17/19

to jenkinsc...@googlegroups.com

Mark Hermon commented on

Brian J Murrell I did some more digging, I was mistaken in saying that it was the #. It looks like parallel stages return out of order when they're in progress. I dug through the returned JSON data and found:

The current run (593):

The previous run (592):

It looks like it gets into this function and then bails out because the Stages aren't in the same order.

I haven't been able to dig any further to see why the stages are returning out of order yet. I could be going in completely the wrong direction.

wim@akimbo.be (JIRA)

unread,

Dec 5, 2019, 12:00:03 PM12/5/19

to jenkinsc...@googlegroups.com

Wim Coenen commented on

I have this problem only while parallel stages are executing.

When the pipeline advances to the next stage without parallelism, I suddenly see past builds again. When the pipeline then advances to a stage containing parallel stages, the past builds disappear again, etc.

mdealer@gmail.com (JIRA)

unread,

Dec 17, 2019, 1:20:04 AM12/17/19

to jenkinsc...@googlegroups.com

Edgars Batna commented on

The stage view should be redone, as it's too flaky and keeps breaking on simple things.

I've seen suggestions to use Blue Ocean, but there is a crucial flaw with this: the Chuck Norris plugin does not support it.

brian.murrell@intel.com (JIRA)

unread,

Dec 17, 2019, 9:31:02 AM12/17/19

to jenkinsc...@googlegroups.com

Brian J Murrell commented on

I've seen suggestions to use Blue Ocean, but there is a crucial flaw with this: the Chuck Norris plugin does not support it.

Blue Ocean is simply not a suitable replacement for Stage View. It has it's own bugs and issues. It's heavy – it can take many (very many in some cases) seconds to load, it's often "out of date" telling me that it's waiting for a stage to start when the stage is well under way having executed many steps already. Those are just the issues off the top of my head.

kivagant@gmail.com (JIRA)

unread,

Feb 4, 2020, 9:02:04 AM2/4/20

to jenkinsc...@googlegroups.com

Eugene G commented on

I really vote for the issue. Is it possible to generate each build with its own headers to avoid comparing titles? A lot of our jobs have steps that are always ordered in different ways and have different stages generated dynamically. The logic that hides previous builds causes huge pain.

kivagant@gmail.com (JIRA)

unread,

Feb 4, 2020, 9:03:03 AM2/4/20

to jenkinsc...@googlegroups.com

Eugene G edited a comment on

I really vote for the issue. Is it possible to generate each build with its own headers to avoid comparing titles? A lot of our jobs have steps that are always ordered in different ways and have different stages generated dynamically. The logic that hides previous builds causes huge pain. Especially when these jobs run in parallel which makes impossible to see even current builds statuses.