While migrating the ci jobs to the new Jenkins instance we detected a lot of issues originating in the naming of test projects inside the integration tests. That was (to my knowledge) never happening on the old CI but the new one seems to act more parallel and hence we get a lot of issues like "project already exists" or "stalemutableregistryexception". A solution is to use the empty default constructor of the FuseProject rule which then generates a more unique name for the generated projects.