|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You could use only the last 10 builds, though this would give less a useful graph: you might as well display information for builds you have at hand. The only “pro” I can think of is that the behavior is more consistent because it would always be showing the last 10 (or however many) builds regardless of what Jenkins had been doing before.
Note that the build history widget loads the most recent 30 builds when you view the job index page, so these would usually be in memory anyway.
The
JENKINS-23945fix, for JUnit results, is to display the trend for loaded builds. (More precisely, for all builds starting with the most recent and continuing backwards so long as they exist on disk and are loaded in memory.)