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

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Major
    • Component/s: locks-and-latches-plugin
    • None
    • Environment:
      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.

            Assignee:
            Unassigned
            Reporter:
            robsimon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: