The JEP is nicely done and very explanatory for anyone who wants to
learn about this new, upcoming capability. I've done a preliminary
review of the four linked draft implementation PRs. They look good so
far. Looks like we should be able to get this feature in nicely without
disrupting anything.
This will be a great connection mechanism to have.
Jeff Thompson
On 11/25/19 10:00 AM, Jesse Glick wrote:
Should have sent a message about this on Friday but Gmail was being
cranky. Anyway:
https://github.com/jenkinsci/jep/pull/250
tl;dr: This lets “inbound” agents (`JNLPLauncher`) make a Remoting
connection to the master via a WebSocket upgrade on the HTTP port
rather than using the TCP port, to simplify Jenkins setup in special
network topologies (including basically any Kubernetes installation).
Currently working at a prototype level.
Comments welcome on either the JEP or the linked draft implementation PRs.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/ad3d25e1-4af9-389f-6326-42727f829f0f%40cloudbees.com.
