[
https://issues.jenkins-ci.org/browse/JENKINS-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161096#comment-161096
]
lestin commented on JENKINS-1163:
---------------------------------
I've seen if you actually want to ask the slave to use the same client name as
the master, you can, using the ${basename}.
But is there a place where i can configure the default to be using ${basename}
or i'll have to do it per job basis?
Thanks.
> Perforce plugin syncs to master instead of slave
> ------------------------------------------------
>
> Key: JENKINS-1163
> URL: https://issues.jenkins-ci.org/browse/JENKINS-1163
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: esakamot
> Assignee: vicsz
>
> Date: Tue, 8 Jan 2008 13:02:48 -0800 (PST)
> From: Eli Sakamoto <e...@autonomy.com>
> Content-Type: text/plain; charset=us-ascii
> Subject: Perforce plugin syncs to master instead of slave
> Hi,
> 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
> machine.
> 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?
> Best regards,
> Eli Sakamoto
> --
> View this message in context:
> http://www.nabble.com/Perforce-plugin-syncs-to-master-instead-of-slave-tp14698703p14698703.html
> Sent from the Hudson users mailing list archive at Nabble.com.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
