[JENKINS-61409] - Update to Remoting 4.3 for WebSocket large payload fix.

[jeffret-b]

See JENKINS-61409.

Also see the Remoting changelog.

Related to jenkinsci/jenkins#4601.

[jglick]

We could just have

ARG VERSION

and then specify the actual version just once in Makefile.

[jeffret-b]

Jesse has a great idea. Do you or someone on the team want to implement that? Or I could see about putting something together.

[jeffret-b]

See if we can get clean rebuild.

[oleg-nenashev]

Jesse has a great idea. Do you or someone on the team want to implement that? Or I could see about putting something together.

We still use the DockerHub Autobuild as a delivery engine. One we move to the Jenkins release environment, we can change the implementation

[jeffret-b]

Looks like some timeout in the build.

[MarkEWaite]

It is looking for an agent with the label windock. There is only one agent with that label currently. It is https://ci.jenkins.io/computer/win2019-a7d1c0/ and it is offline

@slide I'm not clear on the ci.jenkins.io agent labels for Windows machines. I assume windock means a Windows machine that has Docker for Windows installed. Is it also assumed that label means the Windows machine can run Windows Docker images (as opposed to Linux images)?

[slide]

@MarkEWaite, yes there are two different Windows images because most plugins assume Linux when running on an agent with the docker label, also the image is larger when it has docker installed because there is no Windows Server Core sku with docker on Azure.

[slide]

It's only been running for 7 minutes so far, the Windows agents can take some time to spin up, so this time doesn't see out of the ordinary.