Date: Tue, 8 Jan 2008 13:02:48 -0800 (PST)
From: Eli Sakamoto <email@example.com>
Content-Type: text/plain; charset=us-ascii
Subject: Perforce plugin syncs to master instead of slave
I'm running a simple setup with a master running under Winstone and one
slave. Both machines run Linux and have a user and group both named hudson.
The master ssh's into the slave using public key authentication, and seems
to work fine as far as I can tell. I've set up a free-style software project
job named "test" that is tied to the slave and syncs from a dedicated
perforce workspace. I have Let Hudson Manage Workspace View unchecked, One
Time Force Sync checked, and the Depot Path set to "//...". The master's
home directory and the slave's remote FS path are both set to
/home/hudson/.hudson, which are two separate local directories, one on each
When I commence the build, the directory /home/hudson/.hudson/workspace/test
is created on the slave. However, when the actual p4 forced sync starts,
another directory /home/hudson/.hudson/workspace/test is created on the
master and then sync starts populating this directory, leaving the slave
directory empty. As such, when the sync finishes and the compiling starts,
it looks into the empty slave directory and the build fails. Is this the
expected behaviour for the perforce plugin? If not, does anyone know what
would cause this behaviour and how to rectify it?
View this message in context:
Sent from the Hudson users mailing list archive at Nabble.com.