Add support of Remoting connections to masters without Web UI

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

XMLWordPrintable

    • Remoting 3.34

      Currently Remoting agents always require Jenkins master to have a Tcp Agent Listener endpoint. It complicates usage of Remoting with CloudAPI-provided agents together with Jenkinsfile Runner which does not have a fixed Web UI port.

      I propose to add new options to Remoting so that it can connect without polling metadata from the master

       

            Assignee:
            Jeff Thompson
            Reporter:
            Oleg Nenashev
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: