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 t
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:
>
>
