[
https://issues.jenkins-ci.org/browse/JENKINS-12606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Petti resolved JENKINS-12606.
---------------------------------
Resolution: Fixed
Assuming this is no longer an issue.
> Perforce polling can cause infinite build loop.
> -----------------------------------------------
>
> Key: JENKINS-12606
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12606
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Affects Versions: current
> Environment: Windows Server 2008.
> Reporter: Paul M
> Assignee: Rob Petti
>
> When a project that uses Perforce polling is building it appears the
> following can happen:
> 1. The p4 plugin polls for a change.
> 2. A change is found, it starts a build.
> 3. The build takes a long time (say 30mins).
> 4. The p4 plugin polls again for a change (say every min).
> 5. The project is still building.
> 6. At this point the p4 plugin seems to assume there are changes and triggers
> another build.
> 7. Goto 1.
> The message from the polling log during this situation reads:
> Started on 27-Jan-2012 13:55:39
> Looking for changes...
> Using master
> Using master perforce client: XYZ
> Changing P4 Client View from:
> //server/path/... //XYZ/...
> Changing P4 Client View to:
> "//server/path/..." "//XYZ/..."
> Saving modified client XYZ
> Previous build doesn't have Perforce info.
> Workspace not up-to-date.
> Triggering a build.
> Done. Took 0.29 sec
> Changes found
> I think they key info here is the "Previous build doesn't have Perforce
> info." which appears while its still building.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
