Renaming a node over another is possible and destroys both configurations

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

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical
    • Component/s: core
    • Environment:
      Software version: Jenkins ver. 1.635
      Possibly related plug-in: Windows Slaves Plugin
      Java version: 1.8.0_66
      Operating system: Windows Server 2008 R2

      When performing a node name rework, it is possible (partially?) overwrite a node with another one simply by renaming an existing node.

      Steps to reproduce:

      1. Create a node named foo
      2. Create another node named bar
      3. Go to the bar node configuration
      4. Rename it to foo and press Save

      Expected results:

      • An error message.

      Actual results:

      • Node bar replaces foo without any notice
      • Things start to behave wacky: build starts to fail without a reason (see attached edited log, Jenkins-BuildBreakageAfterNodeRename.txt

            Assignee:
            Christopher Simons
            Reporter:
            Helder Magalhães
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: