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 Le mardi 23 août 2022 à 00:23:42 UTC+2, m...@basilcrow.com a écrit : > 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). > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bd7e087f-4cce-4f26-b386-94ebbfb16b85n%40googlegroups.com.
