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

changing of lock-names leads to wrong locks in job configs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • locks-and-latches-plugin
    • None
    • Jenkins v1.415, Locks-and-Latches v0.6

      When I change the name of a lock in the Jenkins configuration then all job configs which contained this lock will fall back to the first lock in the list of the Jenkins configuration.

      It should get either the new name via a rename function or send out a warning which jobs are affected by this change.

          [JENKINS-10311] changing of lock-names leads to wrong locks in job configs

          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
            robsimon robsimon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: