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

Collision with locks-and-latches/lock/foo(1)=1 and locks-and-latches/lock/foo(1)

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • Jenkins ver. 1.527
      Locks-and-latches plugin ver. 0.6

      Job A, B and C share the same lock foo
      Job A is running.
      Job B and C are scheduled to start about the same time.
      The plugin write a log "Collision with locks-and-latches/lock/foo(1)=1 and locks-and-latches/lock/foo(1)" twice every 2 seconds until job A is completed.

      Functionally, the lock seems to handling the queue ok, but the fact that it writes to log twice every 2 seconds seems to create a performance issue for Jenkins.

          [JENKINS-19464] Collision with locks-and-latches/lock/foo(1)=1 and locks-and-latches/lock/foo(1)

          Mark Waite added a comment -

          The Hudson locks and latches plugin is not distributed by the Jenkins update center. It was proposed for deprecation in 2015 and has known blocking issues. It prevents the saving of Jenkins job configurations in Jenkins 2.277.1 and later.

          If someone adopted the plugin, updated it to work with Jenkins 2.277.1 and later, and released a new version, then this issue report could be reopened.

          Mark Waite added a comment - The Hudson locks and latches plugin is not distributed by the Jenkins update center. It was proposed for deprecation in 2015 and has known blocking issues. It prevents the saving of Jenkins job configurations in Jenkins 2.277.1 and later. If someone adopted the plugin, updated it to work with Jenkins 2.277.1 and later, and released a new version, then this issue report could be reopened.

            Unassigned Unassigned
            pok_lau Pok Lau
            Votes:
            6 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: