If you run two Jenkins instances on the same home, then those instances
do not see what the other Jenkins is doing, so you get into a really
weird state. So there's a check that detects that, which is what you saw.
(putting my CloudBees hat on, I can't resist the temptation to mention
that I'm actually working on adding basic high-availability into Jenkins
Enterprise by CloudBees. If you are interested, we can talk more about
that off list.)
On 03/19/2012 06:18 AM, Norman Baumann wrote:
Hey everyone,
Has anybody attempted to run multiple Jenkins instances in a cluster-like
environment?
In order to ensure constant uptime, I wanted to run two Jenkins instances
on the same JENKINS_HOMEDIR. This has worked for a while with the expected
side effects (updates are not recognized until a refresh), but suddently
this error message ocured:
"Error: Jenkins detected that you appear to be running more than one
instance of Jenkins that share the same home directory
'/path/to/jenkins/home/dir'.
This greatly confuses Jenkins and you will likely experience strange
behaviors, so please correct the situation."
I would appreciate some experience data is available?
Best regards,
Norman
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins
