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

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

    Details

    • Type: Bug
    • Status: Open (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

          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.

            People

            • Assignee:
              Unassigned
              Reporter:
              ryanstewart456 Ryan Stewart
            • Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: