Jenkins ver. 1.642

This is occuring on freestyle builds that are triggered by a cron expression and an upstream job (promotions plugin). When those triggers both happen close to each other it seams to "kill" the executor due to the IllegalStateExceptionThese are newer builds (#533, #532) but still its trying to run the [JobName]\builds\405 ,which already exists. Normally, it should trigger #533, #532 newer jobs IDs. We are constantly able to reproduce the issue every time a child job is triggered by the parent job using "Trigger call/builds on another projects" feature.

Exception:

java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs[JobName]\builds\405 already existed; will not overwrite with [JobName] #405
at hudson.model.RunMap.put(RunMap.java:188)
at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1019)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145)
at hudson.model.Executor$1.call(Executor.java:364)
at hudson.model.Executor$1.call(Executor.java:346)
at hudson.model.Queue._withLock(Queue.java:1405)
at hudson.model.Queue.withLock(Queue.java:1270)
at hudson.model.Executor.run(Executor.java:346)

Jenkins in 1.607 (2015/03/30) - Has changes which removes race condition rendering the list of executors (issue 27564) might be causing this race condition issue.

Similar threads:
https://issues.jenkins-ci.org/browse/JENKINS-29268 [Configuration race condition]
https://issues.jenkins-ci.org/browse/JENKINS-26582 [also has this issue for ver 1.621]

Any idea for resolving this issue, we are constantly getting the executer failures states.