Job stuck on jenkins without attributed runner for gemoc project

Summary

Hi

Our jobs seems to be stuck without been able to really get a runner since a few days (there were no error mail so I didn't notice earlier)

https://ci.eclipse.org/gemoc/job/gemoc-studio-integration/job/master/

corresponding jenkins file : https://github.com/gemoc/gemoc-studio-eclipse-integration/blob/master/Jenkinsfile

Is there something changed on the infrastructure so that we need to change the jenkins file ? The only suspicious message ([WARNING] label option is deprecated. To use a static pod template, use the 'inheritFrom' option.) was already present in the previous build that successfully run

I've checked that the docker image exists on docker hub https://hub.docker.com/repository/docker/gemoc/gemoc-jenkins-fat-agent/general

Steps to reproduce

Manually, try to launch a build on the master branch of the

What is the current bug behavior?

Console shows that it tries to assign runner but nothing happen, then assign a new one until global failure

What is the expected correct behavior?

I'd expect some docker image running.

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

Medium This prevents from being able to verify consistently the contributions.