|
||||||||
|
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 understand your need to save space, but Perforce and the p4 plugin were not designed to share workspaces in quite this way.
The server stores a have list (db.have) of the files that have been synced into the workspace. When you use the same workspace with two Jenkins jobs, the p4 plugin switched the workspace root to the Jenkins job build location, but uses the same have list server side. If you set the Workspace root to the same location, then you might have some success, but you must limit the jobs to single execution and use Auto clean/Sync.
Another solution might be to use three Perforce workspaces (each with their own Jenkins jobs) one for the common art assets and the other two for the projects (lets call them A and B). Then use symlinks to bring the art assets into the projects for A and B (or instead of symlinks, update the build rules for the new location).
For future solutions... I'm currently researching FlexClone with Perforce/Jenkins builds; it requires a NetApp storage, but there may be other similar solutions for other storage vendors.