Hi,
I am a Jenkins administrator for a site with not that many jobs, but these
jobs keep a constant rate of massive compiler warnings (~9000 - 10000).
For a particular job for a software with multiple versions the per build
build.xml log file that is generated and kept by Jenkins is around ~13MB.
The analysis.xml containing the compiler warnings is around ~ 8.5 MB. With
14 jobs each keeping 14 days of history brings the total Jenkins has to
scan to ~2.1 G.
Only be removing jobs from the dashboard view made it responsive again. I
still observed some lag switching between other views, but when I had
reduced the amount of jobs it seemed Jenkins was able to keep everything in
core. The "All" pane is still unusable due to this.
The bulk of the build.xml seems to consist out of
~ 89000 lines of cppcheck data
~ 87000 lines of sloccount data
Trimming these sections from the build.xml leaves it only ~ 430 lines
The analysis.xml is around ~183500 lines.
Except for the team fixing the compiler warnings, reducing the amount of
jobs per dashboard view, shorter retention periods for build data, no
graphs in dashboards, deleting old jobs, is there any way in where Jenkins
can be tuned to handle these warning heavy jobs ?
Best Regards,
Ruben van Staveren
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" 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/groups/opt_out.
