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

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.

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.

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 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

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

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

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

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

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

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

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

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?

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.

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

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.