As part of our FinalBuilder script we run some SSH Execute actions that can take a significant time to complete (10-60 minutes). The timeout for those actions is -1, which the dialog documents as “wait until the command completes”. Our existing build machine has FinalBuilder 8.0.0.3364 and the scripts are waiting successfully. I just set up our new machine with FinalBuilder 8.5.0.3497 and even though the scripts are identical it’s now failing with a “Response reading timed out” error with a “Run time” of 00:00:00:073. Other SSH Execute actions with timeouts > 0 are working correctly. Since the dialog caption hasn’t changed, I assume this change of behavior was unintentional.
In case it’s relevant, the old build VM was Windows 10, the new one is Windows 11 24H2, and they’re connecting to a Mac Mini on the same ethernet switch.
It turns our we misread the ssh client library documentation. It has 2 timeout properties, the connection timeout supports 0 or -1 for infinite wait - the command timeout does not.
I have changed the code so that if the command timeout is 0 or -1 then we set the actual command timeout to 24hrs.
This build has the fix - it also includes an updated ssh client library which has several compatibility improvements.