|
||||||||
|
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.
Hi Arpit. Sorry about this. I am looking into it now.
I actually did test this back when I was rejigging things with the build history widget to make it layout a bit better, in that, I created a test job that had a few hundred builds and, to be honest, I could not notice a difference between performance of the new and old layout code. It was dog slow in either case !
How that history widget works is a bit insane anyway. Rendering anything more than 50 or so jobs seems bad UX to me from may perspectives (performance, navigation etc).
I think what Daniel says re the more button only showing a few more builds makes sense. In fact, I would go a step further and implement a paging mechanism whereby you have your standard "Prev" and "Next" buttons in the history widget and you never display more than 50 or so builds. I'm sure someone will have an issue with that though![]()