Miscellaneous Projects » Core testing infrastructure

We have jobs, particularly the ttcn3 dockerized test jobs, which can not run multiple times on the same node as they use static IP addresses and docker refuses to have the same addresses in multiple isolated networks/namespaces.

Right now the "workaround" is to globally block the job. So if any of our TTCN3 bts tests (e.g. master) is running anywhere, we won't do another BTS test (e.g. latest, centos) on any other executor. Particularly since those BTS/BSC tests are taking hours to execute, this is causing significant delays.

There are multiple suggestions in
https://stackoverflow.com/questions/36454130/how-do-i-prevent-two-pipeline-jenkins-jobs-of-the-same-type-to-run-in-parallel-o how to achieve the desired behavior. I of course don't know if any of them work, but it might be worth having a look.