Thanks for the reply Rob. After some thinking over the weekend, over an earlier reply, the options to get around this problem would be to escape the '@' or using the relative path to the files using the P4_CLIENT view.
I will try to modify my setup to reference the files in the P4 command using the relative path for the given P4_CLIENT. I think that this is the best approach. It also verifies that my P4_CLIENT for the given build step is correctly set. Thanks, Mgimza On Fri, Sep 28, 2012 at 8:06 PM, Rob Petti <rob.pe...@gmail.com> wrote: > Sounds like this might potentially be a bug. Can you file a ticket? If you > can't set the PATH on the systems correctly before starting the slave > agents, then you may need to define your P4 installation in jenkins instead. > > On Wednesday, 26 September 2012 23:22:07 UTC-6, Erling Andersen wrote: >> >> Hi >> >> We have had problem with the Perforce plugin on Windows. The issue is >> related to which PATH is used when the the p4 command is run. >> We thought that PATH would have the value defined on the node in Jenkins >> and NOT the PATH value defined on the machine and know by Java. >> We define PATH on each node inside Jenkins on the configure page on the >> nodes. >> >> Is it not possible to define PATH on each node? And should not that >> valued by used by running p4? >> >> Erling >> >> >> >> >>
