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

expose owned lock name(s) through an environment variable

XMLWordPrintable

      I need to know which locks are owned at build time, if possible using a new environment variable such as:
      LOCKS=resource1
      LOCKS=resource1,resource2

      Rationale:
      The lock may also denote a resource identifier, such as a file name, which could be used in build scripts.
      Currently, we have to duplicate such identifiers in manually maintained environment variables.

      Best,
      Régis

        1. locks-env-var.patch
          1.0 kB

          [JENKINS-9069] expose owned lock name(s) through an environment variable

          Régis Desgroppes added a comment -

          Yours to rework.

          Régis Desgroppes added a comment - Yours to rework.

          Régis Desgroppes added a comment -

          No longer using deprecated locks-and-latches plugin: throttle-concurrents plugin does the job.

          Régis Desgroppes added a comment - No longer using deprecated locks-and-latches plugin: throttle-concurrents plugin does the job.

            stephenconnolly Stephen Connolly
            rdesgroppes Régis Desgroppes
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: