|
||||||||
|
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.
Using the same workspace for different jobs is the problem.
Perforce stores a 'have' list entry for each file synced into a workspace. The 'have' list is then used for subsequent syncs. If Perforce already thinks you have a file revision based on the 'have' list, it will not send you that file. Jenkins will use a different workspace root for each job e.g.
c:\jenkins_home\job_1\
c:\jenkins_home\job_2\
If the same Perforce Workspace is used only one 'have' list is maintained, but the updates are now split across different paths.