|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This might seem strange, but the output is correct.
The first line 'in workspace c:\trees\nodes\rsmsnbuild121' is reported by Jenkins. I have no control over the text, it is also true as this is where Jenkins will execute the build. However, as I no longer modify the clients root for Static workspaces the sync command can run anywhere on the machine. As long as the files end up where Jenkins needs them (c:\trees\nodes\rsmsnbuild121), you can use Perforce to sync files to other parts of the system.
I have seen a few customers use this trick to sync, compilers, build tools, IDE's, etc... outside of the build area.