- 
    New Feature 
- 
    Resolution: Fixed
- 
    Minor 
- 
        
- 
        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
- causes
- 
                    JENKINS-59094 Agent tunnel connection issues after ugrading Jenkins to 2.191 -         
- Resolved
 
-         
- relates to
- 
                    JENKINS-28499 tcpSlaveAgentListener not found -         
- Reopened
 
-         
- 
                    JENKINS-54427 Support sidecar containers -         
- Open
 
-         
- links to