|
||||||||
|
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.
So the issue is performance with a very large number of builds. The changes implemented in recent Jenkins make the build history display much better when build names or multiple badges are used, at the cost of additional processing. And I'm fairly sure we want to keep it, as it was pretty bad in some situations before.
A possible solution would be to change how 'more' works to only reveal an additional 50-100 builds each time rather than all of them, assuming the problem is the number of newly added builds to the list, rather than their total number.
I pinged Tom FENNELLY about this, who did all the recent work on the build history widget.