I saw this get thrown from workflow-aggregator-plugin/demo
… jenkins.model.lazy.LazyBuildMixIn newBuild
WARNING: A new build could not be created in job cd/master
java.lang.IllegalStateException: JENKINS-23152: /var/jenkins_home/jobs/cd/branches/master/builds/1 already existed; will not overwrite with cd/master #1
but could not reproduce it—the next time I started the container, all was fine.
I have not yet figured out what could cause this. Something has to be deeply wrong for this to happen—for example, two Job’s with the same name.
I have a suspicion that something in the SCM API 2.x changes caused this. Stephen Connolly any clues?