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

Mercurial poller triggers new build if workspace doesn't exist

    XMLWordPrintable

    Details

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

      Description

      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:

      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.

        Attachments

          Activity

          Hide
          abrucale Aldo Brucale added a comment -

          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.

          Show
          abrucale Aldo Brucale added a comment - 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.
          Hide
          jglick Jesse Glick added a comment -

          Seems to have been fixed in pull request #17 (1.39 plugin), so long as you have caching enabled. (Without caching it is not possible, since Mercurial has no commands to extract arbitrary information from a remote repository.)

          Show
          jglick Jesse Glick added a comment - Seems to have been fixed in pull request #17 (1.39 plugin), so long as you have caching enabled. (Without caching it is not possible, since Mercurial has no commands to extract arbitrary information from a remote repository.)

            People

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

              Dates

              • Created:
                Updated:
                Resolved: