-
Bug
-
Resolution: Fixed
-
Major
-
None
Hi,
I've discovered an issue with the Perforce plugin.
I have a job called "GenerateClassLayout", which is configured to "Let Jenkins Manage Workspace View" and "Clean Workspace before Each Build".
The Poll SCM schedule is set to */2 * * * * - so poll every 2 minutes.
When I check the polling log I see this:
Started on 21-Jul-2011 10:10:42 Looking for changes... Using node: Jenkins Using master perforce client: Jenkins_GenerateClassLayout [JCI] $ "C:\\Program Files\\Perforce\\p4.exe" workspace -o Jenkins_GenerateClassLayout Last sync'd change was 138510 [JCI] $ "C:\\Program Files\\Perforce\\p4.exe" counter change [JCI] $ "C:\\Program Files\\Perforce\\p4.exe" -s changes //Jenkins_GenerateClassLayout/...@138511,@138519 Latest submitted change selected by workspace is 138519 [JCI] $ "C:\\Program Files\\Perforce\\p4.exe" describe -s 138519 [JCI] $ "C:\\Program Files\\Perforce\\p4.exe" -G where //personal/tfields/Live/External/RecastNavigation/DebugUtils/Source/DebugDraw.cpp Triggering a build. Done. Took 0.7 sec Changes found
Syncing all the required files takes longer than 2 minutes so whilst it's still syncing another build is triggered and the polling log contains this:
Started on 21-Jul-2011 10:12:42 Looking for changes... Using node: Jenkins Using master perforce client: Jenkins_GenerateClassLayout [JCI] $ "C:\\Program Files\\Perforce\\p4.exe" workspace -o Jenkins_GenerateClassLayout Previous build doesn't have Perforce info. [JCI] $ "C:\\Program Files\\Perforce\\p4.exe" sync -n Workspace not up-to-date. Triggering a build. Done. Took 0.98 sec Changes found
As you can see the build start time is exactly 2 minutes later. The question is why is this happening?
I suspect it's something to do with the fact that the workspace is not up to date based on this text in the log: "Workspace not up-to-date."
If I change my polling time to 5 minutes, which gives the system plenty of time to sync then all is well - this is not a solution though.
Thanks in advance,
Tom.