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

Add support of Remoting connections to masters without Web UI

    • 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

       

          [JENKINS-53461] Add support of Remoting connections to masters without Web UI

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oleg Nenashev made changes -
          Labels New: jenkinsfileRunner
          Oleg Nenashev made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/remoting/pull/286 (Web Link)" [ 21801 ]
          Oleg Nenashev made changes -
          Link New: This issue relates to JENKINS-54427 [ JENKINS-54427 ]
          Oleg Nenashev made changes -
          Link New: This issue relates to JENKINS-28499 [ JENKINS-28499 ]
          Jeff Thompson made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ] New: Jeff Thompson [ jthompson ]
          Jeff Thompson made changes -
          Released As New: Remoting 3.34
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Jesse Glick made changes -
          Link New: This issue causes JENKINS-59094 [ JENKINS-59094 ]

            jthompson Jeff Thompson
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: