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

locks and latches shouldnt' be global in multi-config

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The locks and latches plugin stops all instances across a grid from running the
      same build. This is not useful in a multi-config setup where you want to run a
      single build across many machines/os's etc. The default should be to obtain a
      lock per config or slave perhaps with an option to make it global.

        Attachments

          Issue Links

            Activity

            Hide
            emmulator emmulator added a comment -

            Yes, matrixlock-${NODE_NAME} would work for me.

            Show
            emmulator emmulator added a comment - Yes, matrixlock-${NODE_NAME} would work for me.
            Hide
            abloom abloom added a comment -

            Regarding locking each configuration separately, isn't that functionality already implemented for Matrix builds via the "Run each configuration sequentially" checkbox? Since that functionality is already supported it does it really make sense to have Locks and Latches duplicate it? Specially at the expense of being able to lock the 'parent' job.

            In our setup we have a need for an exclusive lock for jobs A, B, C and D, where C and D are matrix configurations with dozens of individual, configurations (which need to run in simultaneously). We need to prevent job B from starting while C or D are running. At this time we haven't found a way to accomplish this, but Locks and Latches would seem ideal for the task - if it didn't lock the individual configurations.

            Please reconsider or add an option to provide this support.

            Show
            abloom abloom added a comment - Regarding locking each configuration separately, isn't that functionality already implemented for Matrix builds via the "Run each configuration sequentially" checkbox? Since that functionality is already supported it does it really make sense to have Locks and Latches duplicate it? Specially at the expense of being able to lock the 'parent' job. In our setup we have a need for an exclusive lock for jobs A, B, C and D, where C and D are matrix configurations with dozens of individual, configurations (which need to run in simultaneously). We need to prevent job B from starting while C or D are running. At this time we haven't found a way to accomplish this, but Locks and Latches would seem ideal for the task - if it didn't lock the individual configurations. Please reconsider or add an option to provide this support.
            Hide
            aggamemnon aggamemnon added a comment -

            This issue is also affecting my build environment, as each of our projects in Hudson have around 4 different build configurations, and obviously running them in parallel would be MUCH quicker.

            Show
            aggamemnon aggamemnon added a comment - This issue is also affecting my build environment, as each of our projects in Hudson have around 4 different build configurations, and obviously running them in parallel would be MUCH quicker.
            Hide
            abayer Andrew Bayer added a comment -

            Try using the Throttle Concurrent Builds plugin instead - it properly handles matrix builds in this scenario. https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin

            Show
            abayer Andrew Bayer added a comment - Try using the Throttle Concurrent Builds plugin instead - it properly handles matrix builds in this scenario. https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin
            Hide
            emmulator emmulator added a comment -

            abayer, I don't understand. How does the Throttle Concurrent Builds plugin address the usecase where one wants an exclusive lock between a matrix and a non-matrix build?

            Show
            emmulator emmulator added a comment - abayer, I don't understand. How does the Throttle Concurrent Builds plugin address the usecase where one wants an exclusive lock between a matrix and a non-matrix build?

              People

              Assignee:
              stephenconnolly Stephen Connolly
              Reporter:
              brianf brianf
              Votes:
              8 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: