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

          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: