-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
With over e.g. 200+ builds the generation of trend graphs for duration and test result takes several seconds.
As seen from discussion below, the best solution would be to implement "max builds to show" option also in global config. It should be decided how global configs and job configs interact with each other.
Also disabling the graph altogether can be considered.
[JENKINS-15190] Implement "max builds to show" as a global config
jpiironen
created issue -
| Workflow | Original: JNJira [ 145912 ] | New: JNJira + In-Review [ 176476 ] |
Tatu Kairi
made changes -
| Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
| Assignee | Original: jpiironen [ jpiironen ] | New: Aleksi Simell [ aleksisimell ] |
| Summary | Original: Creation of trend graphs is slow on large number of builds | New: Implement "max builds to show" as a global config |
| Description | Original: With over e.g. 200+ builds the generation of trend graphs for duration and test result takes several seconds. |
New:
With over e.g. 200+ builds the generation of trend graphs for duration and test result takes several seconds.
As seen from discussion below, the best solution would be to implement "max builds to show" option also in global config. Also disabling the graph altogether can be considered. |
| Description |
Original:
With over e.g. 200+ builds the generation of trend graphs for duration and test result takes several seconds.
As seen from discussion below, the best solution would be to implement "max builds to show" option also in global config. Also disabling the graph altogether can be considered. |
New:
With over e.g. 200+ builds the generation of trend graphs for duration and test result takes several seconds.
As seen from discussion below, the best solution would be to implement "max builds to show" option also in global config. It should be decided how global configs and job configs interact with each other. Also disabling the graph altogether can be considered. |