specify:
JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Xmx2048m -Xms256m
-XX:MaxPermSize=1024M"
I’ll see how that goes.
David
From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of JOHNSTON, Rob
Sen
Hi David
If it’s Jenkins itself running out of Perm space then yes, you’ll need to
increase its MaxPermSize JVM setting.
If it’s a particular build or group of build that throws the error (so the
error occurs but Jenkins continues to function), you need to figure out how to
increase the Perm s
shakedown tests to make sure everything is working,
instead of the comprehensive suite.
Any thoughts on that approach?
From: Christian Willman [mailto:cewi...@gmail.com]
Sent: Thursday, 6 March 2014 6:47 PM
To: jenkinsci-users@googlegroups.com
Cc: JOHNSTON, Rob
Subject: Re: Strategies to disk-risk a
Hi list
My group run a large Jenkins instance that many other teams in our organisation
depend on. We want to automate the Jenkins upgrade process which will include a
measure of verification that the upgrade hasn’t broken anything.
I’m thinking of only using LTS releases, backing up the main c
