[JIRA] [core] (JENKINS-29447) Dead Executor due to build number seemingly being reset

[achit...@mercenarytechnology.com (JIRA)]

Title: Message Title

A C created an issue   Jenkins / JENKINS-29447 Dead Executor due to build number seemingly being reset Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Jul/15 9:09 PM Labels: executor Priority: Critical Reporter: A C It appears that somehow the build number is getting stomped. This exception happened on the master node and set a slave to the dead state. The failing jobs had previously been working and the build number should be in the 100s. If it makes a difference, the build in question uses a standard Build Flow + Job DSL architecture, and the failing jobs are ones generated by Job DSL and run in parallel by Build Flow. java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\<project>\builds\1 already existed; will not overwite with <project> #1 at hudson.model.RunMap.put(RunMap.java:189) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at hudson.model.AbstractProject.newBuild(AbstractProject.java:1017) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1216) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor$1.call(Executor.java:335) at hudson.model.Executor$1.call(Executor.java:317) at hudson.model.Queue._withLock(Queue.java:1345) at hudson.model.Queue.withLock(Queue.java:1210) at hudson.model.Executor.run(Executor.java:317) Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.