Failing Windows build on ci.jenkins.io

[martinda]

Hello,

We have added a new step to the pipeline-utility-steps-plugin but the Windows build fails after about an hour: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fpipeline-utility-steps-plugin/detail/PR-162/1/pipeline/92#step-98-log-158

It looks like a timeout issue. Is this an infra issue? Could someone look at it and help us please?

Thanks,

Martin d'Anjou

[Basil Crow]

I restarted your build at
https://ci.jenkins.io/job/Plugins/job/pipeline-utility-steps-plugin/job/PR-162/2/
and the second build ran to completion (with a test failure in your
new test).

[Damien Duportal]

Thanks Basil for restarting the build!

After a quick check, there was no issue on the infrastructure.

But the build reached the timeout of 1 hour (default for plugins as per https://github.com/jenkins-infra/pipeline-library/blob/master/vars/buildPlugin.groovy#L13) which stopped the build.

The underlying infrastructure is a Windows Container (with Maven 3.8.4 and a JDK8) running in Azure Container Instance services: it seems that the baseline performance for this service is having a lot of differences between 2 identical tasks (can 2x faster!) which explains the timeout. The infrastructure team is studying how to improve this situation, thanks for raising this concern.

Damien, for the Infra team