Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60995

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: In Review (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.176.2.3
      Blue ocean 1.17.0
      Groovy pipeline
    • Similar Issues:

      Description

      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

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

      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.

        Attachments

          Issue Links

            Activity

            ryanstewart456 Ryan Stewart created issue -
            ryanstewart456 Ryan Stewart made changes -
            Field Original Value New Value
            Attachment image-2020-02-06-11-24-13-909.png [ 50130 ]
            ryanstewart456 Ryan Stewart made changes -
            Attachment image-2020-02-06-11-28-39-728.png [ 50129 ]
            ryanstewart456 Ryan Stewart made changes -
            Attachment image-2020-02-06-11-42-54-433.png [ 50131 ]
            ryanstewart456 Ryan Stewart made changes -
            Attachment image-2020-02-06-11-43-50-478.png [ 50132 ]
            ryanstewart456 Ryan Stewart made changes -
            Description 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.
            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.
            ryanstewart456 Ryan Stewart made changes -
            Description 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.
            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.
            ryanstewart456 Ryan Stewart made changes -
            Description 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.
            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.
            ryanstewart456 Ryan Stewart made changes -
            Description 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.
            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.
            Hide
            roalter Luis Roalter added a comment -

            Looks the same here. But not for all builds. Old builds (before upgrading) still show the triggered build sections.

            Show
            roalter Luis Roalter added a comment - Looks the same here. But not for all builds. Old builds (before upgrading) still show the triggered build sections.
            Hide
            peterwallerarm Peter Waller added a comment -

             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.
            Show
            peterwallerarm Peter Waller added a comment -  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.
            Hide
            eliminator Eli Entelis added a comment -

            I experiance the same problem, is there an estimation when this will be fixed?

            Show
            eliminator Eli Entelis added a comment - I experiance the same problem, is there an estimation when this will be fixed?
            Hide
            insulind Dave Quinn added a comment -

            Any movement on getting this fixed?

            Show
            insulind Dave Quinn added a comment - Any movement on getting this fixed?
            allan_burdajewicz Allan BURDAJEWICZ made changes -
            Remote Link This issue links to "pipeline-build-step-plugin #54 (Web Link)" [ 26790 ]
            allan_burdajewicz Allan BURDAJEWICZ made changes -
            Remote Link This issue links to "blue-ocean #2187 (Web Link)" [ 26791 ]
            allan_burdajewicz Allan BURDAJEWICZ made changes -
            Remote Link This issue links to "blue-ocean #2188 (Web Link)" [ 26792 ]
            Show
            allan_burdajewicz Allan BURDAJEWICZ added a comment - This is being reviewed: https://github.com/jenkinsci/pipeline-build-step-plugin/pull/54 https://github.com/jenkinsci/blueocean-plugin/pull/2187 https://github.com/jenkinsci/blueocean-plugin/pull/2188 (backport to 1.24)
            vlatombe Vincent Latombe made changes -
            Assignee Vincent Latombe [ vlatombe ]
            vlatombe Vincent Latombe made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            vlatombe Vincent Latombe made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            vlatombe Vincent Latombe made changes -
            Remote Link This issue links to "pipeline-build-step #54 (Web Link)" [ 26793 ]
            vlatombe Vincent Latombe made changes -
            Remote Link This issue links to "blueocean #2187 (Web Link)" [ 26794 ]
            vlatombe Vincent Latombe made changes -
            Remote Link This issue links to "blueocean #2187 (Web Link)" [ 26794 ]
            vlatombe Vincent Latombe made changes -
            Remote Link This issue links to "pipeline-build-step-plugin #54 (Web Link)" [ 26790 ]
            Hide
            jonathand131 Jonathan Delizy added a comment -

            Hi,

            Following some plugins update, the call currentBuild.getBuildCauses('hudson.model.Cause$UpstreamCause') in my pipeline groovy script doesn't return the expected values anymore, but it works if I replace it with currentBuild.getBuildCauses('org.jenkinsci.plugins.workflow.support.steps.build.BuildUpstreamCause').

             

            I suspect it is due to changes made in PR#54.

            Perhaps getBuildCauses filtering should be changed to also include causes that are subclasses of the given type.

            Show
            jonathand131 Jonathan Delizy added a comment - Hi, Following some plugins update, the call currentBuild.getBuildCauses('hudson.model.Cause$UpstreamCause') in my pipeline groovy script doesn't return the expected values anymore, but it works if I replace it with currentBuild.getBuildCauses('org.jenkinsci.plugins.workflow.support.steps.build.BuildUpstreamCause') .   I suspect it is due to changes made in PR#54 . Perhaps getBuildCauses filtering should be changed to also include causes that are subclasses of the given type.
            kleini Marcus Klein made changes -
            Link This issue causes JENKINS-66367 [ JENKINS-66367 ]
            Hide
            felipecassiors Felipe Santos added a comment -

            Just wanted to mention that this issue is still happening with Blue Ocean 1.25.1 and Pipeline Build Step 2.15.

            Show
            felipecassiors Felipe Santos added a comment - Just wanted to mention that this issue is still happening with Blue Ocean 1.25.1 and Pipeline Build Step 2.15.

              People

              Assignee:
              vlatombe Vincent Latombe
              Reporter:
              ryanstewart456 Ryan Stewart
              Votes:
              18 Vote for this issue
              Watchers:
              18 Start watching this issue

                Dates

                Created:
                Updated: