Description

The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)

Open the jenkins-bugs multi-branch pipeline folder and index the branches

Wait until at least one of the pipeline jobs completes

Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)

The parent folder does still show the "worst status" when it is configured (see ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.

Patrick Wolf We need to discuss this one. The ability to configure a custom folder icon was only exposed by accident in the original implementation. With 2.0.x this was locked down as the API to lock it down was made available. To support the customization would require adding some sort of organization folder property that allows delegating the configuration to the child projects (as child projects are read-only, so would need configuration at the organization folder level).

In short, getting a consistent UI for this that works for both raw multi-branch projects and multi-branch projects in an org folder is not a trivial solution, and given that the design is that the avatar be displayed in the status icon rather than an aggregate status, I am inclined to mark this as WONTFIX. On the other hand, I can see the utility for some users in being able to get the aggregate status... WDYT?

Stephen Connolly
added a comment - 2017-02-27 14:35 Patrick Wolf We need to discuss this one. The ability to configure a custom folder icon was only exposed by accident in the original implementation. With 2.0.x this was locked down as the API to lock it down was made available. To support the customization would require adding some sort of organization folder property that allows delegating the configuration to the child projects (as child projects are read-only, so would need configuration at the organization folder level).
In short, getting a consistent UI for this that works for both raw multi-branch projects and multi-branch projects in an org folder is not a trivial solution, and given that the design is that the avatar be displayed in the status icon rather than an aggregate status, I am inclined to mark this as WONTFIX. On the other hand, I can see the utility for some users in being able to get the aggregate status... WDYT?