For our current version of Jenkins, 1.456 the library version remoting-2.12 is used.
This fix was tested on the clone ci.* instance, https://ec2-184-72-153-99.compute-1.amazonaws.com/jenkins/ and since it didn't break anything we will deploy it to the production and closely observe whether it fixes the problem or not (since this bug could not be reproduced on our test instance under any circumstances).
The proposed fix is in the Jenkins' remoting library, the code is available here https:/ /code.launchpad .net/~linaro- infrastructure/ jenkins- remoting/ linaro- trunk
For our current version of Jenkins, 1.456 the library version remoting-2.12 is used. /ec2-184- 72-153- 99.compute- 1.amazonaws. com/jenkins/ and since it didn't break anything we will deploy it to the production and closely observe whether it fixes the problem or not (since this bug could not be reproduced on our test instance under any circumstances).
This fix was tested on the clone ci.* instance, https:/