[JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true - #130
Conversation
|
We will need to update the Windows side as well (https://github.com/jenkinsci/docker-jnlp-slave/blob/master/jenkins-agent.ps1) |
|
Yes, I did not try that yet but I could. |
oleg-nenashev
left a comment
There was a problem hiding this comment.
Please also update README
JENKINS_WEB_SOCKET=true environment variable
oleg-nenashev
left a comment
There was a problem hiding this comment.
Looks good to me, but the upstream pull request in Remoting needs to be released first
JENKINS_WEB_SOCKET=true environment variableJENKINS_WEB_SOCKET=true environment variable
Yes, this is on hold until the core changes are released. |
JENKINS_WEB_SOCKET=true environment variable
oleg-nenashev
left a comment
There was a problem hiding this comment.
https://github.com/jenkinsci/remoting/releases/tag/remoting-4.0 must be integrated and released in the parent image: https://github.com/jenkinsci/docker-slave . Otherwise this feature will not work
Sure. I presume someone like @jeffret-b would be doing this as a routine task. |
|
I was hoping to get to that today, but may have more pressing tasks. |
|
I think there is no rush. This change is needed for people who wish to use WebSocket transport for agents managed by the |
|
I managed to squeeze it in before lunch. The PRs are up. |
|
So can you merge & release this @jeffret-b, or whoever is maintaining this repo? |
|
I don't have permission in this repository. Maybe @slide or @oleg-nenashev |
|
@MarkEWaite thanks! Now can you can a release please? 3.40-1...master |
|
I would like to leave this for @oleg-nenashev to release, since he's released the most recent several versions of it and I've never released a version. If @oleg-nenashev has not been able to release it by tomorrow, I'll attempt the release. |
|
Sorry that I missed this one @jglick. As I look at the repository, the release process is not immediately clear to me. I'll talk with @oleg-nenashev tomorrow and learn how to release from this repository. |
|
I am not sure either. It may suffice to just create a tag and wait for Docker Hub automated builds to kick in. |
|
IIUC from the |
|
The linux publishing should be done on dockerhub builds, though I am not sure how the tagging for specific versions takes place. For the Windows versions, we are publishing them via trusted.ci, we do not currently do a version specific release, I would need to look into that. |
|
on it |
|
The 4.0.1-1 release is now available and ready to use. A CONTRIBUTING document has also been added which includes a video link to a session that describes the release process. |
$ docker run --rm jenkinsci/jnlp-slave:4.0.1-1 2>&1 | fgrep -i websocket
-webSocket : Make a WebSocket connection to Jenkins🎉 |
Fix issue with paths when using MinGit busybox
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…lick/websocket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
…socket [JEP-222] Enable WebSocket mode by passing JENKINS_WEB_SOCKET=true
See JEP-222. Alternative to #129. Works with jenkinsci/remoting#357. Requires #147.