JEP draft posted: WebSocket Services

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

JEP draft posted: WebSocket Services

Jesse Glick-4
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3kAyx0oqVSTGEkf8PRA84i803VBKw5pUe9oT0RqJ1XLg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: JEP draft posted: WebSocket Services

Kohsuke Kawaguchi
Administrator
Yay, something I've long been advocating for!! Super exciting.

On Mon, Nov 25, 2019 at 9:06 AM Jesse Glick <[hidden email]> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3kAyx0oqVSTGEkf8PRA84i803VBKw5pUe9oT0RqJ1XLg%40mail.gmail.com.


--
Kohsuke Kawaguchi

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4zxwFvRfQHbntgUmkKHet3n5F2-L0EFFWa%3DSMF2B_8-JQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: JEP draft posted: WebSocket Services

Jeff Thompson
In reply to this post by Jesse Glick-4
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ad3d25e1-4af9-389f-6326-42727f829f0f%40cloudbees.com.