[JIRA] (JENKINS-60995) Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart created an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17 Issue Type: Bug Assignee: Unassigned Attachments: image-2020-02-06-11-24-13-909.png, image-2020-02-06-11-28-39-728.png Components: blueocean-plugin Created: 2020-02-06 11:41 Environment: Jenkins 2.176.2.3 Blue ocean 1.17.0 Groovy pipeline Priority: Major Reporter: Ryan Stewart When triggering a downstream job BlueOcean normally displays the following section with a link to the downstream job, as introduced in JENKINS-38339 However, after upgrading to BlueOcean 1.17 this behaviour seems to have regressed: There a lot of comments on the original ticket JENKINS-38339 listing the same issue. I am aware that this was once an issue for declarative pipelines and fixed as part of https://github.com/jenkinsci/blueocean-plugin/pull/1918/files But I am running legacy groovy pipeline. Add Comment

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

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart updated an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17

Change By: Ryan Stewart Attachment: image-2020-02-06-11-42-54-433.png

Add Comment

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart updated an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17

Change By: Ryan Stewart Attachment: image-2020-02-06-11-24-13-909.png

Add Comment

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart updated an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17

Change By: Ryan Stewart Attachment: image-2020-02-06-11-28-39-728.png

Add Comment

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart updated an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17 Change By: Ryan Stewart

When triggering a downstream job BlueOcean normally displays the following section with a link to the downstream job, as introduced in JENKINS-38339

!image-2020-02-06-11- 24 42 - 13 54 - 909 433 .png|width= 446 776 ,height= 124 186 !

However, after upgrading to BlueOcean 1.17 this behaviour seems to have regressed:

!image-2020-02-06-11- 28 43 - 39 50 - 728 478 .png|width= 513 1250 ,height= 314 301 !

There a lot of comments on the original ticket JENKINS-38339 listing the same issue. I am aware that this was once an issue for declarative pipelines and fixed as part of [https://github.com/jenkinsci/blueocean-plugin/pull/1918/files] But I am running legacy groovy pipeline.

Add Comment

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart updated an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17

Change By: Ryan Stewart Attachment: image-2020-02-06-11-43-50-478.png

Add Comment

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart updated an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17 Change By: Ryan Stewart

When triggering a downstream job BlueOcean normally displays the following section with a link to the downstream job, as introduced in JENKINS-38339

!image-2020-02-06-11-42-54-433.png|width=776,height=186!

However, after upgrading to BlueOcean 1.17 this behaviour seems to have regressed:

!image-2020-02-06-11-43-50-478.png|width=1250,height=301!

There a lot of comments on the original ticket JENKINS-38339 listing the same issue. I am aware that this was once an issue for declarative pipelines and fixed as part of [https://github.com/jenkinsci/blueocean-plugin/pull/1918/files] But I am running legacy groovy pipeline.

It is important to note that this does not always happen: sometimes a run will show the link, then when the exact same run is re-ran again it fails to show. I have found this issue with both sequential and parallel pipelines where jobs are kicked off.

Add Comment

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart updated an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17 Change By: Ryan Stewart

I have encountered an issue that severely limits the usability of the BlueOcean plugin when used with downstream jobs.

When triggering a downstream job BlueOcean normally displays the following section with a link to the downstream job, as introduced in JENKINS-38339 !image-2020-02-06-11-42-54-433.png|width=776,height=186! However, after upgrading to BlueOcean 1.17 this behaviour seems to have regressed: !image-2020-02-06-11-43-50-478.png|width=1250,height=301! There a lot of comments on the original ticket JENKINS-38339 listing the same issue. I am aware that this was once an issue for declarative pipelines and fixed as part of [https://github.com/jenkinsci/blueocean-plugin/pull/1918/files] But I am running legacy groovy pipeline.   It is important to note that this does not always happen: sometimes a run will show the link, then when the exact same run is re-ran again it fails to show. I have found this issue with both sequential and parallel pipelines where jobs are kicked off.

Add Comment

[ryanstewart456@gmail.com (JIRA)]

Ryan Stewart updated an issue

Jenkins / JENKINS-60995 Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17 Change By: Ryan Stewart

I have encountered an issue that severely limits the usability of the BlueOcean plugin when used with downstream jobs.   When triggering a downstream job BlueOcean normally displays the following section with a link to the downstream job, as introduced in JENKINS-38339 !image-2020-02-06-11-42-54-433.png|width=776,height=186! However, after upgrading to BlueOcean 1.17 this behaviour seems to have regressed: !image-2020-02-06-11-43-50-478.png|width=1250,height=301!

There are a lot of comments on the original ticket JENKINS-38339 listing the same issue.

I am aware that this was once an issue for declarative pipelines and fixed as part of [https://github.com/jenkinsci/blueocean-plugin/pull/1918/files] But I am running legacy groovy pipeline.   It is important to note that this does not always happen: sometimes a run will show the link, then when the exact same run is re-ran again it fails to show. I have found this issue with both sequential and parallel pipelines where jobs are kicked off.

Add Comment

[roalter@gmail.com (JIRA)]

Luis Roalter commented on JENKINS-60995

Re: Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17 Looks the same here. But not for all builds. Old builds (before upgrading) still show the triggered build sections.

Add Comment

[peter.waller@arm.com (JIRA)]

Peter Waller commented on JENKINS-60995

Re: Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17

A few observations: The links seem to be missing in particular if there is any failing build within the whole pipeline. The source data exists on disk in the jenkins XML database, so I believe this is a presentation bug. Stuart Rowe did some additional investigation in this other ticket, and seems to have come close to localizing the bug.

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)