g/browse/JENKINS-8754>)
We're using 1.510 and upgrading every week if it worth to upgrade
(checking the changelog first).
How long do you keep the build history? Do you have artifacts? do you
delete them periodically?
Viktor Konnyu <mailto:vkon...@chemaxon.com>
April 15, 20
l the memory usage as well via parameters like:
JAVA_ARGS="-Djava.awt.headless=true -Xms1g -Xmx10g -XX:MaxPermSize=1G
-XX:+UseParNewGC"
This is a very optimal setup for us. ~100 nodes, ~200 jobs with
thousands of tests (heavy loaded jenkins cluster running 0-24 and
building continuously)
Hi,
Jenkins seems to consume an awful lot of memory. As I understand it is
due to keeping build logs in memory for one. My question is what other
factors influence jenkins' memory consumption and what can I do about
it? Also, is there a way to flush the memory on demand or force a GC
without
Hi,
My problem is that files generated by static analysis plugins (mainly
checkstyle warnings) take up lots of space and they are kept for each
build. Is there something I can do about it except for disabling the
plugins (and fixing the warnings)? As it stands, for a simple job I end
up over