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

reconnect agent after configuration change

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None

      When configuration of node was changed agent should be reconnected.

      Especially when IP/hostname adres has been changed it still using old one until user manually do disconnect and connect again.

          [JENKINS-71946] reconnect agent after configuration change

          Markus Winter added a comment -

          It's not so easy, e.g. when one just changes the label of an agent, availability or usage there should not be a disconnect.
          Changing the hostname/IP of an agent seems to be to wrong approach anyway. In that case I would recommend to create a new agent and delete the old one.

          Markus Winter added a comment - It's not so easy, e.g. when one just changes the label of an agent, availability or usage there should not be a disconnect. Changing the hostname/IP of an agent seems to be to wrong approach anyway. In that case I would recommend to create a new agent and delete the old one.

          Pawel Xj added a comment -

          Actually, this affected our team twice, when creating new node by copy existing one and changing name and IP.

          For some reason node has been started with old address.

          Pawel Xj added a comment - Actually, this affected our team twice, when creating new node by copy existing one and changing name and IP. For some reason node has been started with old address.

            Unassigned Unassigned
            xjjx Pawel Xj
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: