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

Multibranch Pipeline projects do not expose build status

      It seems that the "Multibranch Pipeline" projects do not expose the build status inside views and as a side effect it also makes impossible to track them via cc.xml - which is generated based on the view.

      Obviously that the next question would be: which status should be displayed because multibranch pipelines are like folder of jobs.

      I guess that it should expose a single branch build status, by default master of the first one detected but being able to determine a different one.

          [JENKINS-33885] Multibranch Pipeline projects do not expose build status

          Sorin Sbarnea created issue -
          Sorin Sbarnea made changes -
          Link New: This issue is blocking JENKINS-33645 [ JENKINS-33645 ]
          Matthew DeTullio made changes -
          Component/s Original: multi-branch-project-plugin [ 21127 ]
          Matthew DeTullio made changes -
          Labels New: multibranch
          Matthew DeTullio made changes -
          Assignee Original: Matthew DeTullio [ mjdetullio ] New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Labels Original: multibranch New: folders multibranch

          Jesse Glick added a comment -

          I have no idea what cc.xml is or what it is being generated by, but AFAIK there is nothing missing in Pipeline or multibranch per se. As you can see from your screenshot, the weather icon does represent the aggregate status of the branch projects inside the folder, just like it would for any other folder.

          Perhaps this just boils down to some old tool not being folder-aware.

          Jesse Glick added a comment - I have no idea what cc.xml is or what it is being generated by, but AFAIK there is nothing missing in Pipeline or multibranch per se. As you can see from your screenshot, the weather icon does represent the aggregate status of the branch projects inside the folder, just like it would for any other folder. Perhaps this just boils down to some old tool not being folder-aware.
          Jesse Glick made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 169884 ] New: JNJira + In-Review [ 198721 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-general [ 21692 ]

            jglick Jesse Glick
            ssbarnea Sorin Sbarnea
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: