Remoting "-tunnel" option is obsolete, redesign needed

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

XMLWordPrintable

      JnlpAgentURLResolver behaves strangely when the "tunnel" option is set. It checks correctness of ports and other parameters returned by the Master and takes results into account when selecting the master to connect... but actually never uses these parameters because they are overridden by tunnel settings

            Assignee:
            Unassigned
            Reporter:
            Oleg Nenashev
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: