[JIRA] Commented: (JENKINS-8173) SCM polling always fails using Perforce plugin due to "workspace offline" and causes infinite build loop

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (JENKINS-8173) SCM polling always fails using Perforce plugin due to "workspace offline" and causes infinite build loop

JIRA noreply@jenkins-ci.org

    [ http://issues.jenkins-ci.org/browse/JENKINS-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146593#comment-146593 ]

Rob Petti commented on JENKINS-8173:
------------------------------------

As mentioned, simply changing the output of requiresWorkspaceForPolling will not fix this in all cases. It is trivial to change it, but it will have far reaching consequences, such as polling simply not working at all in most configurations. This is because polling would then be executed on the master with the slave's perforce options, which would only match in the ideal case.

Martin, can you please file a new issue for the NPE (and be sure to include the log dump and perforce plugin version). You might also want to try the latest version, since you are really out of date.

> SCM polling always fails using Perforce plugin due to "workspace offline" and causes infinite build loop
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-8173
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8173
>             Project: Jenkins
>          Issue Type: Bug
>          Components: perforce
>            Reporter: paulmoran
>            Assignee: Rob Petti
>            Priority: Critical
>
> 1. Set up an "in demand" slave.
> 2. Set up a project that only builds on that slave
> 3. The slave will go offline
> 4. The SCM poll will see that the workspace is offline and trigger a new build
> 5. The slave comes online, the build completes
> 6. The slave goes back offline again as in 3.
> 7. And here the infinite build loop happens since we now send up back at 4
> I'm not sure why Hudson is trying to get the content of the workspace? The perforce plugin knows the last change list number used for the last build, so it should also know by polling perforce that the last changlist number is different and so a build should be triggered?
> In our environment each slave is actually a virtual machine controlled by scripts, after a build completes its taken offline so checking the workspace will NEVER work. This completely breaks our setup because builds are only set to trigger for SCM changes.
> When a slave is brought back online the VM is reverted to its snapshot to ensure the build is "clean", so again this means checking the workspace content will always fail.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira