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

    • Bug
    • Status: In Review (View Workflow)
    • Major
    • Resolution: Unresolved
    • blueocean-plugin
    • None
    • Jenkins 2.176.2.3
      Blue ocean 1.17.0
      Groovy pipeline

    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

            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.

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

            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.
            xjjx Pawel Xj added a comment -

            Still present in Blue Ocean 1.25.2, Jenkins 2.319.1

            xjjx Pawel Xj added a comment - Still present in Blue Ocean 1.25.2, Jenkins 2.319.1
            sfryffdc Stephen Fry added a comment -

            vlatombe allan_burdajewicz any idea if this is going to be progressed? Is there anything I can do to help expedite a fix here? Thanks

            sfryffdc Stephen Fry added a comment - vlatombe allan_burdajewicz any idea if this is going to be progressed? Is there anything I can do to help expedite a fix here? Thanks
            robmcgee Rob McGee added a comment -

            Also seeing this in Jenkins 2.346.3 using Blue Ocean 1.25.8. 

            robmcgee Rob McGee added a comment - Also seeing this in Jenkins 2.346.3 using Blue Ocean 1.25.8. 

            People

              vlatombe Vincent Latombe
              ryanstewart456 Ryan Stewart
              Votes:
              22 Vote for this issue
              Watchers:
              24 Start watching this issue

              Dates

                Created:
                Updated: