-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-68542] [WebSocket] Capture cookie returned by server and reuse for reconnection attempts #539
Conversation
…se for reconnection attempts Cherry-picked from cc32c3b
I guess I'll need |
I believe so yes. I do not have access. Maybe @timja does? |
I thought that the transition to JEP-229 was complete enough on this repository that a new release will be created once the pull request is merged. The only case that I know for generating the release on trusted.ci.jenkins.io is if we require a signed jar file. Is a signed jar file required with this change? I have permission to launch releases of remoting on trusted.ci.jenkins.io, if needed. |
@MarkEWaite this is a case for a backport on a version predating signature removal and JEP-229 setup. |
Thanks @Vlatombe . I had missed that the destination branch is a backport. Once it is merged, I believe that I can launch the build of the backport. |
Unsure what is going on with the windows build though... |
https://release.ci.jenkins.io ftr, requires VPN access and release team membership. (I see Mark has volunteered to trigger it, make sure you release the backport and not the master branch) |
@MarkEWaite |
JENKINS-68542
Cherry-picked from cc32c3b (#537)
Remoting 4.13 is the version pinned on Jenkins LTS 2.332 and 2.346