[JIRA] (JENKINS-42511) ISE from RunMap.put

[email protected] (JIRA) Mon, 06 Mar 2017 15:27:13 -0800

Title: Message Title

Jesse Glick updated an issue

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
	at hudson.model.RunMap.put(RunMap.java:188)
	at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:185)
	at org.jenkinsci.plugins.workflow.job.WorkflowJob.createExecutable(WorkflowJob.java:260)
	at hudson.model.Executor$1.call(Executor.java:355)
	at hudson.model.Executor$1.call(Executor.java:337)
	at hudson.model.Queue._withLock(Queue.java:1368)
	at hudson.model.Queue.withLock(Queue.java:1229)
	at hudson.model.Executor.run(Executor.java:337)
 
                                                            

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?

Change By:	Jesse Glick
Summary:	a job has a build but no history ISE from RunMap . put
Priority:	Minor Critical
Labels:	core pipeline

Add Comment

This message was sent by Atlassian JIRA

--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42511) ISE from RunMap.put

Reply via email to