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

Renaming a node over another is possible and destroys both configurations

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: core
    • Labels:
    • 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
    • Similar Issues:

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              csimons Christopher Simons
              Reporter:
              heldermagalhaes Helder Magalhães
            • Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: