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

          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.

          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.

          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.

          Jesse Glick added a comment -

          Or any AbstractFolder.

          Better would be to have core define some kind of extension point for populating this view cell, or simply use ItemGroup.getAllJobs itself.

          Jesse Glick added a comment - Or any AbstractFolder . Better would be to have core define some kind of extension point for populating this view cell, or simply use ItemGroup.getAllJobs itself.

          Implementing as reporting the results of the last folder computation.

          Stephen Connolly added a comment - Implementing as reporting the results of the last folder computation.

          Mark Waite added a comment - - edited

          Is this also related to the recent regression described in JENKINS-41785 (Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder'), or are those completely independent issues?

          Mark Waite added a comment - - edited Is this also related to the recent regression described in JENKINS-41785 (Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder'), or are those completely independent issues?

          markewaite These are completely separate issues. The original ask in this issue is to have the last success and last failure (which currently report N/A) return the last success and last failure for any job in the folder.

          More correct IMHO is to actually report the last success / last failure of the folder computation (otherwise you will not see the failed computations) This is what I am fixing here. The other issue is separate and AIUI is a result of the folder icon customization not respecting the custom status icon possibility

          Stephen Connolly added a comment - markewaite These are completely separate issues. The original ask in this issue is to have the last success and last failure (which currently report N/A) return the last success and last failure for any job in the folder. More correct IMHO is to actually report the last success / last failure of the folder computation (otherwise you will not see the failed computations) This is what I am fixing here. The other issue is separate and AIUI is a result of the folder icon customization not respecting the custom status icon possibility

          Jesse Glick added a comment -

          It seems you are hijacking this reasonable RFE (which does, in fact, apply to any folder—not just multibranch) with a distinct RFE (to show some overview of indexing status) which should have been filed separately.

          Jesse Glick added a comment - It seems you are hijacking this reasonable RFE (which does, in fact, apply to any folder—not just multibranch) with a distinct RFE (to show some overview of indexing status) which should have been filed separately.

          Well I see reporting the last failure of a child job as being contradictory to reporting the last failure of the computation. And with computations, we need to be reporting those last failures

          Stephen Connolly added a comment - Well I see reporting the last failure of a child job as being contradictory to reporting the last failure of the computation. And with computations, we need to be reporting those last failures

          Jesse Glick added a comment -

          I see reporting the last failure of a child job as being contradictory to reporting the last failure of the computation.

          Why? These seem orthogonal reports.

          Jesse Glick added a comment - I see reporting the last failure of a child job as being contradictory to reporting the last failure of the computation. Why? These seem orthogonal reports.

          Because they both belong in the same column. We cannot display the last scan success in the same column as the last child item success

          Stephen Connolly added a comment - Because they both belong in the same column. We cannot display the last scan success in the same column as the last child item success

          Jesse Glick added a comment -

          I would expect a new ListViewColumn for last scan information. But CC hrmpw.

          Jesse Glick added a comment - I would expect a new ListViewColumn for last scan information. But CC hrmpw .

          Stephen Connolly added a comment - - edited

          As of Jenkins 2.50, the build now button will have the tool tip Schedule a Scan for ___

          To my mind the Lass Success, Last Failure and Last Duration columns logically refer to the action in the "Build" Now column.

          As such, I believe adding new columns would only confuse users... we'd have a `Last Success` and a `Last Computation Success`, a `Last Failure` and a `Last Computation Failure`, a `Last Duration` and a `Last Computation Duration`... plus what would we do for e.g. Compact Columns?

          I think if there is a use case for seeing the info for child builds, that should be a Last Child Build status column

          Stephen Connolly added a comment - - edited As of Jenkins 2.50, the build now button will have the tool tip Schedule a Scan for ___ To my mind the Lass Success, Last Failure and Last Duration columns logically refer to the action in the "Build" Now column. As such, I believe adding new columns would only confuse users... we'd have a `Last Success` and a `Last Computation Success`, a `Last Failure` and a `Last Computation Failure`, a `Last Duration` and a `Last Computation Duration`... plus what would we do for e.g. Compact Columns? I think if there is a use case for seeing the info for child builds, that should be a Last Child Build status column

          jglick Is this really what you are suggesting to expose the computation status?

          Stephen Connolly added a comment - jglick Is this really what you are suggesting to expose the computation status?

          Patrick Wolf added a comment -

          I really don't like adding more columns just for "Last Computation Success" etc. That will really confuse users that don't know what that means and it widens display for no reason.

          We should either show the last success of a successful indexing or we shouldn't show anything. Showing the last successful build of a branch nested 3 levels deep provides almost no meaningful information. The column title seems pretty generic and doesn't have to be a build.

          Patrick Wolf added a comment - I really don't like adding more columns just for "Last Computation Success" etc. That will really confuse users that don't know what that means and it widens display for no reason. We should either show the last success of a successful indexing or we shouldn't show anything. Showing the last successful build of a branch nested 3 levels deep provides almost no meaningful information. The column title seems pretty generic and doesn't have to be a build.

          Code changed in jenkins
          User: Stephen Connolly
          Path:
          src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java
          src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java
          src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java
          src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.jelly
          src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties
          src/main/resources/com/cloudbees/hudson/plugins/folder/computed/PseudoRun/sidepanel.jelly
          http://jenkins-ci.org/commit/cloudbees-folder-plugin/8eac7c15023886a86ce839dfb809c37736fff674
          Log:
          JENKINS-37369 Expose the last computation for computed folders

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/PseudoRun/sidepanel.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/8eac7c15023886a86ce839dfb809c37736fff674 Log: JENKINS-37369 Expose the last computation for computed folders

          Code changed in jenkins
          User: Stephen Connolly
          Path:
          src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java
          http://jenkins-ci.org/commit/cloudbees-folder-plugin/695f4b651427dc683a6c08c96e8a750904c56d03
          Log:
          JENKINS-37369 Use HttpResponses.redirectViaContextPath

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/695f4b651427dc683a6c08c96e8a750904c56d03 Log: JENKINS-37369 Use HttpResponses.redirectViaContextPath

          Code changed in jenkins
          User: Stephen Connolly
          Path:
          src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java
          src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java
          src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java
          src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.jelly
          src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties
          src/main/resources/com/cloudbees/hudson/plugins/folder/computed/PseudoRun/sidepanel.jelly
          http://jenkins-ci.org/commit/cloudbees-folder-plugin/4dda5fcd52893c83dc9f6d0a4b4950f53d816fc9
          Log:
          Merge pull request #87 from stephenc/jenkins-37369

          JENKINS-37369 Expose the last computation for computed folders

          Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/9645813fbe71...4dda5fcd5289

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/PseudoRun/sidepanel.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/4dda5fcd52893c83dc9f6d0a4b4950f53d816fc9 Log: Merge pull request #87 from stephenc/jenkins-37369 JENKINS-37369 Expose the last computation for computed folders Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/9645813fbe71...4dda5fcd5289

          Jesse Glick added a comment -

          I suppose this should be Fixed? Or, more accurately, Will Not Fix and a separate issue marked as Fixed which reflects what was done instead?

          Jesse Glick added a comment - I suppose this should be Fixed? Or, more accurately, Will Not Fix and a separate issue marked as Fixed which reflects what was done instead?

          Kevin Lyda added a comment -

          Ugh. So when I see all my projects on the main view the last success and failure columns relate to some low-level implementation detail of Jenkins instead of the results of my builds?

          Let me just note that as a user this is, at best, a user-indifferent design decision.

          Disappointing.

          Kevin Lyda added a comment - Ugh. So when I see all my projects on the main view the last success and failure columns relate to some low-level implementation detail of Jenkins instead of the results of my builds? Let me just note that as a user this is, at best, a user-indifferent design decision. Disappointing.

          Jesse Glick added a comment -

          Yes it seems weird, but pretty much all UI design work these days goes into Blue Ocean.

          Jesse Glick added a comment - Yes it seems weird, but pretty much all UI design work these days goes into Blue Ocean.

          Sverre Moe added a comment -

          It seems this is halfway implemented. We get information on Last Success and Last Duration, but not Last Failure, that is still showing N/A.

          Sverre Moe added a comment - It seems this is halfway implemented. We get information on Last Success and Last Duration, but not Last Failure, that is still showing N/A.

          Liam Newman added a comment - - edited

          With Blue Ocean no longer being worked on, this should probably be back on the table.

          Liam Newman added a comment - - edited With Blue Ocean no longer being worked on, this should probably be back on the table.

          Kamil Mackow added a comment -

          Agreed. Our org has switched exclusively to multibranch jobs and the complete lack of overall status observability is laughable. Please reconsider properly surfacing the relevant data points in this view.

          Kamil Mackow added a comment - Agreed. Our org has switched exclusively to multibranch jobs and the complete lack of overall status observability is laughable. Please reconsider properly surfacing the relevant data points in this view.

          mesa added a comment -

          This should be re-opened. We think it is not acceptable that we must go into each multi-branch pipeline job in order to find out if it has been run. Causes a lot of extra clicking and is time-consuming.

          mesa added a comment - This should be re-opened. We think it is not acceptable that we must go into each multi-branch pipeline job in order to find out if it has been run. Causes a lot of extra clicking and is time-consuming.

          Kevin Lyda added a comment -

          I long ago switched to gitlab ci/issues. I have one instance of using Jenkins with GitHub, but when I have some spare time I'll switch to GitHub Workflow. It really doesn't seem like Jenkins has a future. The devs just don't seem interested in modern git workflows. Which is fine - there are still places using subversion and I'm sure even cvs. But that's a shrinking subset.

          Kevin Lyda added a comment - I long ago switched to gitlab ci/issues. I have one instance of using Jenkins with GitHub, but when I have some spare time I'll switch to GitHub Workflow. It really doesn't seem like Jenkins has a future. The devs just don't seem interested in modern git workflows. Which is fine - there are still places using subversion and I'm sure even cvs. But that's a shrinking subset.

          Sam Darwin added a comment -

          Hi,

          Jenkins is very nice software.
          On the main screen, all multibranch pipelines says "Last Failure": "N/A" .  Can the time of the last failure be shown?

          Thanks.

          Sam Darwin added a comment - Hi, Jenkins is very nice software. On the main screen, all multibranch pipelines says "Last Failure": "N/A" .  Can the time of the last failure be shown? Thanks.

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

              Created:
              Updated: