• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: blueocean-plugin
• Labels:

  None
• Environment:

  Jenkins 2.176.2.3
  Blue ocean 1.17.0
  Groovy pipeline

1. 

   image-2020-02-06-11-43-50-478.png

   24 kB

   2020-02-06 11:43

2. 

   image-2020-02-06-11-42-54-433.png

   27 kB

   2020-02-06 11:42

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

Ryan Stewart created issue - 2020-02-06 11:41

Ryan Stewart made changes - 2020-02-06 11:42

Attachment

Original: image-2020-02-06-11-24-13-909.png [ 50130 ]

Ryan Stewart made changes - 2020-02-06 11:42

Attachment

Original: image-2020-02-06-11-28-39-728.png [ 50129 ]

Ryan Stewart made changes - 2020-02-06 11:42

Attachment

New: image-2020-02-06-11-42-54-433.png [ 50131 ]

Ryan Stewart made changes - 2020-02-06 11:43

Attachment

New: image-2020-02-06-11-43-50-478.png [ 50132 ]

Ryan Stewart made changes - 2020-02-06 11:43

Description

Original: 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-13-909.png|width=446,height=124! However, after upgrading to BlueOcean 1.17 this behaviour seems to have regressed: !image-2020-02-06-11-28-39-728.png|width=513,height=314! 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.

New: 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.

Ryan Stewart made changes - 2020-02-06 11:45

Description

Original: 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.

New: 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.

Ryan Stewart made changes - 2020-02-06 11:46

Description

Original: 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.

New: 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.

Ryan Stewart made changes - 2020-02-06 11:46

Description

Original: 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.

New: 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.

Allan BURDAJEWICZ made changes - 2021-06-24 04:37

Remote Link

New: This issue links to "pipeline-build-step-plugin #54 (Web Link)" [ 26790 ]

Allan BURDAJEWICZ made changes - 2021-06-24 04:38

Remote Link

New: This issue links to "blue-ocean #2187 (Web Link)" [ 26791 ]

Load more newer history items