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

Multibranch Pipeline projects do not expose build status

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

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

            Show
            jglick 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.
            Hide
            ssbarnea Sorin Sbarnea added a comment -

            I think it went even worse: now the normal pipeline jobs (non multi-branch) are no longer exposing themselves into cc.xml – somehow it seems that only old freetype jobs are exposing their status in cc.xml

            cc.xml is the only cross "standard API" (cross CI compatible ) way to obtain the build status of a job. It is supported by most CI systems. 

            Jesse Glick, is even documented on https://wiki.jenkins.io/display/JENKINS/Monitoring+Jenkins

            PS. There a at least a dozen of tools supporting it and Jenkins team should not drop this and ask them to use vendor-specific API when we already had a vendor free API for at least a decade if not more.

             

            Show
            ssbarnea Sorin Sbarnea added a comment - I think it went even worse: now the normal pipeline jobs (non multi-branch) are no longer exposing themselves into cc.xml – somehow it seems that only old freetype jobs are exposing their status in cc.xml cc.xml is the only cross "standard API" (cross CI compatible ) way to obtain the build status of a job. It is supported by most CI systems.  Jesse Glick , is even documented on https://wiki.jenkins.io/display/JENKINS/Monitoring+Jenkins PS. There a at least a dozen of tools supporting it and Jenkins team should not drop this and ask them to use vendor-specific API when we already had a vendor free API for at least a decade if not more.  
            Hide
            jglick Jesse Glick added a comment -

            Whatever it is, after JENKINS-46942 you are free to maintain it.

            Show
            jglick Jesse Glick added a comment - Whatever it is, after  JENKINS-46942 you are free to maintain it.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: