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

Locks-and-latches plugin not locking properly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Critical Critical
    • locks-and-latches-plugin
    • None
    • Platform: All, OS: All

      The locks-and-latches plugin fails to lock each slave when running a matrix job
      running on several slaves. Instead, the job is run on each slave in parallel.

      Stephen Connolly has posted these follow ups on the mailing list:

      "I think the other issue is a bug in ResourceLists in the core of
      Hudson. I'll write a unit test to check my theory and maybe commit
      the fix. I have a work-around in the Locks and Latches plugin that
      should detect when the bug is fixed in the core and disable it's
      workaround!"

      "I have filed an issue and checked-in JUnit tests with regards to the
      resources issue:

      https://hudson.dev.java.net/issues/show_bug.cgi?id=1080

      When these are fixed that might fix the matrix issue. The RFE may
      still need some work, if somebody can raise the RFE that way I'll
      remember to get back to it when the core is fixed.

      -Stephen"

          [JENKINS-1083] Locks-and-latches plugin not locking properly

          fhoare added a comment -

          We're seeing this problem of latches and locks not working correctly running
          parallel builds on a single server (no slaves). In fact we see exactly the
          problem described in https://hudson.dev.java.net/issues/show_bug.cgi?id=1579
          which has been closed as a duplicate of this.

          fhoare added a comment - We're seeing this problem of latches and locks not working correctly running parallel builds on a single server (no slaves). In fact we see exactly the problem described in https://hudson.dev.java.net/issues/show_bug.cgi?id=1579 which has been closed as a duplicate of this.

          mdonohue added a comment -

          Moving to 'locks-and-latches' subcomponent

          mdonohue added a comment - Moving to 'locks-and-latches' subcomponent

          gregallen added a comment -

          Information here seems relevant:
          http://www.nabble.com/Login-Problems-tt23478350.html#a23501510

          However, removing %APPDATA%\Subversion* did not seem to help me.

          gregallen added a comment - Information here seems relevant: http://www.nabble.com/Login-Problems-tt23478350.html#a23501510 However, removing %APPDATA%\Subversion* did not seem to help me.

          Kohsuke Kawaguchi added a comment -

          This came up in a conversation with mrooney.

          Kohsuke Kawaguchi added a comment - This came up in a conversation with mrooney.

          Kohsuke Kawaguchi added a comment -

          also see issue #4359

          Kohsuke Kawaguchi added a comment - also see issue #4359

          jminne added a comment -

          I saw a post that mentioned this issue might be fixed.
          I just wanted to note that I am still seeing the basic lock failure behavior from hudson-1579 on build 1.347. The changelogs do not show anything that might have fixed the lock. https://hudson.dev.java.net/changelog.html

          jminne added a comment - I saw a post that mentioned this issue might be fixed. I just wanted to note that I am still seeing the basic lock failure behavior from hudson-1579 on build 1.347. The changelogs do not show anything that might have fixed the lock. https://hudson.dev.java.net/changelog.html

          robertredd added a comment -

          I'm having this same issue in release 1.409.

          If I have Job A being built and Job B and C are in the queue all sharing the same lock, then once A finishes, jobs B and C start in parallel even though all three jobs share the same lock.

          robertredd added a comment - I'm having this same issue in release 1.409. If I have Job A being built and Job B and C are in the queue all sharing the same lock, then once A finishes, jobs B and C start in parallel even though all three jobs share the same lock.

          Krip added a comment -

          I confirm this bug is present in 1.417 version with the exact same case as above:

          Job A having jobs B and C (sharing the same lock) in queue, when A finishes, B and C starts simultaneously and run in parallel.

          Krip added a comment - I confirm this bug is present in 1.417 version with the exact same case as above: Job A having jobs B and C (sharing the same lock) in queue, when A finishes, B and C starts simultaneously and run in parallel.

          Andrew Bayer added a comment -

          Please check out the Throttle Concurrent Builds plugin - https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin. It uses more modern APIs in Jenkins and is actively maintained.

          Andrew Bayer added a comment - Please check out the Throttle Concurrent Builds plugin - https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin . It uses more modern APIs in Jenkins and is actively maintained.

          jminne added a comment - - edited

          Has it been decided that locks and latches is being deprecated in favor of Project Categories in the throttle-concurrents plugin?

          jminne added a comment - - edited Has it been decided that locks and latches is being deprecated in favor of Project Categories in the throttle-concurrents plugin?

            kohsuke Kohsuke Kawaguchi
            crleblanc crleblanc
            Votes:
            25 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: