-
-
Notifications
You must be signed in to change notification settings - Fork 274
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-61409] Websockets: Use AbstractByteBufferCommandTransport to transport messages #373
Conversation
Incrementals is down 😢
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good if it solves the problem. Have you tested it manually to make sure it does that?
Other than the changelog, do we need to do anything else to properly convey information about this breaking change? This feature is considered beta so I don't know that we need to rev the major version. (And we had a discussion not long ago about how useful that is anyway.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
At a minimum we will need to release a new Docker image, and update the |
@Vlatombe , have you tested this in a running environment? It looks like it should work but I just want to check. |
@jeffret-b yes |
Great. I'll mark it ready for merge and try to get it released before too long. |
And do not forget
after which @Vlatombe or I can
|
Coming up |
First Docker PR at jenkinsci/docker-agent#110. After the first one builds, I'll submit the other one. |
Second Docker PR at jenkinsci/docker-inbound-agent#153. |
… transport messages (#373) * Split message when over max size * Should be private * [JENKINS-61409] Use AbstractByteBufferCommandTransport * Log message length
See JENKINS-61409.
Fixes support of websocket messages more than 64kb long.
See downstream jenkinsci/jenkins#4596