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

Multibranch Pipeline: Last build information is not propagated to Jenkins View

      The build information Last Success, Last Failure and Last Duration is not propagated to the Jenkins view. The Jenkins view showing the multibranch pipeline folder always shows N/A. The latest built branch should propagate this build information to the outside view.

          [JENKINS-37369] Multibranch Pipeline: Last build information is not propagated to Jenkins View

          Sverre Moe created issue -
          Sverre Moe made changes -
          Attachment New: jenkinspipeline1.png [ 33604 ]
          Sverre Moe made changes -
          Attachment New: jenkinspipeline2.png [ 33605 ]
          Jesse Glick made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: workflow-multibranch-plugin [ 21465 ]

          Jesse Glick added a comment -

          The view columns are defined in core, and do not handle folders.

          Jesse Glick added a comment - The view columns are defined in core, and do not handle folders.
          Jesse Glick made changes -
          Component/s Original: branch-api-plugin [ 18621 ]
          Jesse Glick made changes -
          Labels Original: Pipeline New: folders multibranch

          Colin Bennett added a comment -

          It is definitely unintuitive to have the last success/last failure value be N/A for multibranch pipeline jobs.

          One thing that I often do is sort all Jenkins jobs by last failure to see what the recently failing builds are on the server. I'm not sure how I can do this with multibranch pipeline jobs.

          Colin Bennett added a comment - It is definitely unintuitive to have the last success/last failure value be N/A for multibranch pipeline jobs. One thing that I often do is sort all Jenkins jobs by last failure to see what the recently failing builds are on the server. I'm not sure how I can do this with multibranch pipeline jobs.
          Colin Bennett made changes -
          Link New: This issue is related to JENKINS-32974 [ JENKINS-32974 ]

          We could have ComputedFolder provide getLastFailedBuild() and getLastSuccessfulBuild() methods returning pseudo Build objects referring to the computation... so that at least those columns display relevant information w.r.t. the last time the organization was scanned.

          Stephen Connolly added a comment - We could have ComputedFolder provide getLastFailedBuild() and getLastSuccessfulBuild() methods returning pseudo Build objects referring to the computation... so that at least those columns display relevant information w.r.t. the last time the organization was scanned.

            Unassigned Unassigned
            djviking Sverre Moe
            Votes:
            4 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated: