Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12404

Mercurial poller triggers new build if workspace doesn't exist


    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: mercurial-plugin
    • Labels:
    • 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
    • Similar Issues:



      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:

      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

      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.



          zaytsev Yury Zaytsev created issue -
          jglick Jesse Glick made changes -
          Field Original Value New Value
          Status Open [ 1 ] Resolved [ 5 ]
          Assignee Kohsuke Kawaguchi [ kohsuke ] Willem Verstraeten [ willemv ]
          Resolution Fixed [ 1 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 142770 ] JNJira + In-Review [ 190260 ]


            • Assignee:
              willemv Willem Verstraeten
              zaytsev Yury Zaytsev
            • Votes:
              1 Vote for this issue
              1 Start watching this issue


              • Created: