|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
So Señor Beck complained that he was getting sunny days on folders that had no builds, and IIRC we fixed that for him by making this health metric report as empty.
My view is that the other columns do not make sense to have such values as last success, last failure, last duration as - in the general case - you cannot guarantee that they reflect the same job.
My view is thus that the correct thing to do for those columns is report as N/A. While it is certainly possible to change the plugin to render a value for these columns, you should be aware that such a change can significantly affect performance, as with nested folders you would effectively end up querying the entire tree for every page rendering (or else you would be caching the result and displaying potentially out of date values or causing high CPU/disk load)... once again the venerable Señor Beck and his folders of folders of folders full of 7000+ jobs will find the performance problem for you... so if you are suggesting a patch in this regard, I strongly recommend testing said patch for performance regressions with a master that has multiple folders with 1,000's of jobs each with at least 10 builds and a random mix of success/failure... oh and don't cheat by using an SSD... use spinning metal as it helps find the performance issues better