[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view

14 views
Skip to first unread message

careje@gmail.com (JIRA)

unread,
Apr 23, 2019, 11:03:02 AM4/23/19
to jenkinsc...@googlegroups.com
Jeff Care created an issue
 
Jenkins / Bug JENKINS-57158
Pipeline is green but shows red in stage view
Issue Type: Bug Bug
Assignee: Sam Van Oort
Attachments: green_red.JPG, support_2019-04-23_14.58.31.zip
Components: pipeline-stage-view-plugin
Created: 2019-04-23 15:02
Priority: Minor Minor
Reporter: Jeff Care

We had a build complete successfully; it shows green when viewing the details for that particular build and in the list of builds for that job. However, in the stage view for the job, that particular build shows red. Screenshot attached.

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

chanukov@gmail.com (JIRA)

unread,
Jun 3, 2019, 4:29:03 PM6/3/19
to jenkinsc...@googlegroups.com
Alon Chanukov updated an issue
Change By: Alon Chanukov
Attachment: Screen Shot 2019-06-03 at 1.27.23 PM.png
Attachment: Screen Shot 2019-06-03 at 1.26.54 PM.png

chanukov@gmail.com (JIRA)

unread,
Jun 3, 2019, 4:35:02 PM6/3/19
to jenkinsc...@googlegroups.com
Alon Chanukov commented on Bug JENKINS-57158
 
Re: Pipeline is green but shows red in stage view

I also had this happen to me in prod twice in the 24 hours since I upgraded to latest started happening after we took in the Jenkins LTS.

This has happened with both regular pipeline and multi branch
we upgraded 
pipeline-stage-tags-metadata 1.3.2
pipeline-stage-view 2.10
On Smithers Staging pipeline-stage-tags-metadata 1.3.8
On Smithers Staging pipeline-stage-view 2.11
among many other plugins, though those seem most applicable
We also moved from 2.89.3 LTS to 2.164.3LTS

PR pipelines

chanukov@gmail.com (JIRA)

unread,
Jun 3, 2019, 4:36:01 PM6/3/19
to jenkinsc...@googlegroups.com
Alon Chanukov edited a comment on Bug JENKINS-57158
I also had this happen to me in prod twice in the 24 hours since I upgraded to latest started happening after we took in the Jenkins LTS.

This has happened with both regular pipeline and multi branch
we upgraded 
pipeline-stage-tags-metadata 1.3.2
pipeline-stage-view 2.10
On Smithers Staging pipeline-stage-tags-metadata 1.3.8
On Smithers Staging pipeline-stage-view 2.11
among many other plugins, though those seem most applicable
We also moved from 2.89.3 LTS to 2.164.3LTS






!Screen Shot 2019-06-03 at 1.27.23 PM.png! PR pipelines

chanukov@gmail.com (JIRA)

unread,
Jun 3, 2019, 4:51:55 PM6/3/19
to jenkinsc...@googlegroups.com
Alon Chanukov edited a comment on Bug JENKINS-57158
I also had this happen reported to me in prod twice in the 24 hours since I upgraded to latest started happening after we took in the Jenkins LTS.


This has happened with both regular pipeline and multi branch
we upgraded 
pipeline-stage-tags-metadata 1.3.2
pipeline-stage-view 2.10
On Smithers Staging pipeline-stage-tags-metadata 1.3.8
On Smithers Staging pipeline-stage-view 2.11
among many other plugins, though those seem most applicable
We also moved from 2.89.3 LTS to 2.164.3LTS

chanukov@gmail.com (JIRA)

unread,
Jun 3, 2019, 4:52:21 PM6/3/19
to jenkinsc...@googlegroups.com

sverre.moe@gmail.com (JIRA)

unread,
Aug 5, 2019, 4:34:03 AM8/5/19
to jenkinsc...@googlegroups.com

We have noticed the same on our Multibranch pipelines. All stages are good, but Stage View still shows the build as failed. It is very rare when it occurs.

jon.sten@gmail.com (JIRA)

unread,
Sep 19, 2019, 7:48:02 AM9/19/19
to jenkinsc...@googlegroups.com
Jon Sten commented on Bug JENKINS-57158

A user ran into the same problem. I did some quick debugging and it the problem is not on the client side. The rest API call incorrectly reports back failure. On the server side I found that calling RunExt.createNew() provides a RunExt with correct status, while RunExt.create() returns a cached RunExt with its status set to failure. I have no idea how that RunExt with incorrect status ended up in the cache. Would be interesting to know it it was had failure status when initially created or had success as initial result but the field was altered by some other code. No one knows...

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

marat@slonopotamus.org (JIRA)

unread,
Dec 26, 2019, 2:44:04 AM12/26/19
to jenkinsc...@googlegroups.com
Marat Radchenko resolved as Duplicate
 

Duplicate of JENKINS-43556

Change By: Marat Radchenko
Status: Open Resolved
Resolution: Duplicate
Reply all
Reply to author
Forward
0 new messages