[
https://issues.jenkins-ci.org/browse/JENKINS-12404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161566#comment-161566
]
Aldo Brucale commented on JENKINS-12404:
----------------------------------------
I'm getting the same behaviour for jobs that run on master nodes, both with
version 1.457 and with LTS 1.447.1 of Jenkins. Everytime I restart Jenkins, the
workspaces are not available, and builds are triggered. On both machines i'm
running mercurial 2.1.
> Mercurial poller triggers new build if workspace doesn't exist
> --------------------------------------------------------------
>
> Key: JENKINS-12404
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12404
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Affects Versions: current
> Environment: Master: RHEL 6.2 / Jenkins ver. 1.424.2 / Mercurial
> plugin 1.38
> Slave: Fedora Core 15 i386 / workspaces located on a tmpfs mount
> Reporter: Yury Zaytsev
> Assignee: Kohsuke Kawaguchi
>
> Hi!
> I have workspaces on my slaves on tmpfs, so every time I reboot a slave the
> workspace, of course, disappears. Now git and svn work totally fine with
> that, but mercurial triggers a new build if the workspace doesn't exist and
> leaves an entry like that in the polling log:
> {quote}
> This page captures the polling log that triggered this build.
> Started on Jan 12, 2012 10:30:55 PM
> No workspace is available, so can't check for updates.
> Scheduling a new build to get a workspace.
> Done. Took 14 ms
> Changes found
> {quote}
> This is very annoying, because sometimes I need to reboot the slaves to apply
> kernel updates etc. and tmpfs is just so much faster than using a
> non-volatile memory.
--
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
