[
https://issues.jenkins-ci.org/browse/JENKINS-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Czachur updated JENKINS-13372:
------------------------------------
Summary: Add "process last N builds for trend" to "Configure System"
Jenkns page. (was: Add "process last N builds for trend" in jenkins
configuration.)
> Add "process last N builds for trend" to "Configure System" Jenkns page.
> -------------------------------------------------------------------------
>
> Key: JENKINS-13372
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13372
> Project: Jenkins
> Issue Type: Bug
> Components: performance-plugin
> Affects Versions: current
> Environment: Performance Plugin 1.7
> Reporter: Piotr Czachur
> Assignee: Manuel Carrasco
>
> Generating trend graphs in case there are hundreds of builds is very resource
> intensive task. Currently there is an option for setting this limit in
> browser cookie (btw I have just filled issue - it doesn't work) but before
> user set it to explicit value, all available builds are taken into
> consideration. This can be very bad and block Jenkins from responding because
> it's crazy busy parsing gigs of data.
> Cookie has also important disadventage: can expire, be cleared and is
> attached to one browser. If user logs in from another location limit setting
> is lost.
> My proposition is to add this limit to Jenkins "Configure System" page just
> like it's done for many popular plugins.
> Cheers!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
