[ https://issues.jenkins-ci.org/browse/JENKINS-11222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159626#comment-159626 ]
Guillermo Schwarz commented on JENKINS-11222: --------------------------------------------- Today I reproduced the problem using Ubuntu 10.4, Tomcat 6, Jenkins ver. 1.452. If I select to it run every minute (periodical execution) it runs with no problems. If I select to poll, it never runs. > Mercurial Plugin does not support SCM polling on slaves > ------------------------------------------------------- > > Key: JENKINS-11222 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11222 > Project: Jenkins > Issue Type: Bug > Components: mercurial > Affects Versions: current > Environment: Windows 7 32bit > Reporter: Britain Crooker > Assignee: Kohsuke Kawaguchi > > Using 1.433 of Jenkins, 1.37 of plugin. > Windows 7 32bit master jenkins install. Windows 7 32bit slave jenkins > install, launched by manually running JNLP from the slave. Created job in > Jenkins which is associated to only run on the slave. The job is configured > with a Mercurial repository. If I configure the job to trigger based on SCM > changes, I get this in the Mercurial polling log: > Started on Oct 5, 2011 9:26:37 AM > No workspace is available, so can't check for updates. > Done. Took 3 ms > No changes > The job has previously run fine and the workspace exists on the slave. The > job is configured to download the repository with a subdirectory called > 'source' in the workspace. The Remote FS Root on the slave is set to: > c:\jenkins\jobs > The workspace for the job exists as: > c:\jenkins\jobs\workspace\<job name>\source -- 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