This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      The current implementation of Pipeline lock step allows to block a single resource.

      It should be extended to cover all the functionality of the plugin (applicable to non-freestyle jobs) such as blocking resources by label or request a lock for N resources.

      The DSL must be something like this:

      lock (resources: ['resource1', 'resource2']) {
        ... execution block ...
      }
      

      or

      lock (label: 'my-resources') {
        ... execution block ...
      }
      

      The behavior of the label parameter would be equivalent to:

      lock (resources: ['resource3', 'resource4']) { // if both resource3 and resource4 are labeled as 'my-resources'
        ... execution block ...
      }
      

            Assignee:
            Antonio Muñiz
            Reporter:
            Antonio Muñiz
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: