-
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
[JENKINS-53461] Add support of Remoting connections to masters without Web UI
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Labels | New: jenkinsfileRunner |
Remote Link | New: This issue links to "https://github.com/jenkinsci/remoting/pull/286 (Web Link)" [ 21801 ] |
Link | New: This issue relates to JENKINS-54427 [ JENKINS-54427 ] |
Link | New: This issue relates to JENKINS-28499 [ JENKINS-28499 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] | New: Jeff Thompson [ jthompson ] |
Released As | New: Remoting 3.34 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
We're running Jenkinsfile Runner on a Kubernetes cluster and use the Kubernetes plugin to dynamically spawn new agents. JNLP connections to the master failed and as a quick workaround, we've opened the HTTP port of the Jenkinsfile Runner. Changing Remoting for this is of course the cleaner solution.
oleg_nenashev Any idea when you will continue working on this topic?