[Jenkins-infra] Your plugin builds can start in seconds, help me test container instances

[R. Tyler Croy]

I've noticed that Pipeline is failing to cope with the ACI agents. It looks
like our old friend "withEnv" is causing troubles, see the attached image. This
was from a Pipeline which I needed to forcibly kill after it had run for 3
days!


My first hypothesis is that there is something about the latency of the
remoting channel to the Azure Container Instances that is causing Pipeline to
simply fail to timeout properly and get stuck.

My second hypothesis is that the agent is actually disappearing, and Pipeline
is not coping with that fact properly.


Andrew, from the Pipeline perspective, are there any things which come to mind
that we could enable to help isolate this issue further?



Cheers
--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: withenv-failure.png
Type: image/png
Size: 167488 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20190316/abe9e136/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 871 bytes
Desc: OpenPGP digital signature
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20190316/abe9e136/attachment-0001.asc>