|
||||||||
|
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.
I actually do have the workspace roots set to the same location, the problem is that the db have is being updated but not actually syncing files, this seems like a bug, since it definitely detects the changes in the depot, but doesn't actually update the files on disk.
I've gotten around this issue by having one job that does the syncing that is called from the other jobs, and when that completes, the jobs run whatever steps the user originally requested. It's annoying, and a little obfuscated, but we can still limit executors meaningfully enough to let things happen in serial they way they currently need to on this box.
We're doing some work internally to bring online a massive storage array, but that introduces other issues with having the files synced and replicated or referenced on the server.
Thanks for the response!