Cloud agent provisioning errors due to Remoting behaviour change

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

XMLWordPrintable

    • Remoting 3.33, jenkins-2.182

      This change https://github.com/jenkinsci/remoting/pull/193/commits/69f9ebe72c608e14745fb3fc5f8d9e4c65758d89 is modifying the behaviour of the agent connection cycle.

      Retrying the connection even when the agent is not yet created in the master was something a cloud implementation could rely on (one of our proprietary implementations does).

      IMHO this was a breaking change. There should be at least one way to keep the previous behaviour (with a new parameter, or maybe reusing the existent "noReconnect").

            Assignee:
            Jeff Thompson
            Reporter:
            Antonio Muñiz
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: