[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma edited a comment on JENKINS-32152 Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) We have fixed this issue. Posting the cause and fix here to help out others.ROOT CAUSE: This issue was caused by the upgrade we performed recently on Jenkins. If the upgrade caused Jenkins to forget date/time and build numbers in history. This reset of build number counters is causing conflicts in the promotions. SUGGESTED FIX: To fix this we should manually go into the ‘C:\Program Files (x86)\Jenkins\jobs**\promotions folder and remove numerical historical folders that are greater than the current promoted build number. This will alleviate the issue entirely. This fix worked in our case. 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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma commented on JENKINS-32152 Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) We have fixed this issue. Posting the cause and fix here to help out others. ROOT CAUSE: This issue was caused by the upgrade we performed recently on Jenkins. If the upgrade caused Jenkins to forget date/time and build numbers in history. This reset of build number counters is causing conflicts in the promotions. SUGGESTED FIX: To fix this we should manually go into the ‘C:\Program Files (x86)\Jenkins\jobs**\promotions folder and remove numerical historical folders that are greater than the current promoted build number. This will alleviate the issue entirely. 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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Labels: Build BuildExecutor BuildNumber DEAD Promotions 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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma resolved as Fixed Jenkins / JENKINS-32152 java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Status: Open Resolved Assignee: Riddhi Sharma Resolution: Fixed 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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title
Riddhi Sharma edited a comment on JENKINS-32152
Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Thanks Jesse for the suggestion. We have used already tried _ Reload Configuration from Disk _ multiple times but the problem still remains and this is happening when we are trying to use the promoted builds plugin to trigger the child jobs. I wanted to understand what is exactly making the builds throw java.lang.IllegalStateException {panel:title=Exception Lines}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){panel}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)
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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma commented on JENKINS-32152 Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) We have used _ Reload Configuration from Disk _ but the problem still remains and this is happening when we are trying to use the promoted builds plugin to trigger the child jobs. I wanted to understand what is exactly making the builds throw java.lang.IllegalStateException Exception Lines 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.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) 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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title
Riddhi Sharma edited a comment on JENKINS-32152
Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Thanks Jesse for the suggestion. We have already tried _ Reload Configuration from Disk _ multiple times but the problem still remains and this is happening when we are trying to use the promoted builds plugin to trigger the child jobs. I wanted to understand what is exactly making the builds throw java.lang.IllegalStateException {panel:title=Exception Lines}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){panel} at hudson specifically when trying to create new Build . 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)
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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title
Riddhi Sharma edited a comment on JENKINS-32152
Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Thank you Daniel for the response. No, we couldn't find any files named "atomic" in the jobs directory or entire jenkins directory. Using Set Next Build Number needs manual input to set the next build number, which we do not want. This is surprising that setting up the next increment build number is jenkins core functionality where we are facing issue while using Promotions (promoted builds plugin - version 2.19 though 2.24.1 is available. Would it be good to do the update?Also, if we look at the error message below, the illegal state exception is happening and build executor are getting dead when SEVERE: Unexpected executor death because it found the builds 18 already existing and could not overwrite. {panel:title=Error}java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\build.pii.A.trunk\promotions\STEP 1 - Promote to DEV\builds\18 already existed; will not overwrite with build.pii.A.trunk/promotion/STEP 1 - Promote to DEV #18 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){panel}
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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title
Riddhi Sharma edited a comment on JENKINS-32152
Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
No, coudn couldn 't find any files named "atomic" in the jobs directory or entire jenkins directory. Using Set Next Build Number needs manual input to set the next build number, which we dont do not want. This is surprising that setting up the next increment build number is jenkins core functionality where we are facing issue while using Promotions (promoted builds plugin - verison version 2.19 though 2.24.1 is available. Would it be good to do the update?Also, if we look at the error message below, the illegal state exception is happening and build executor are getting dead when SEVERE: Unexpected executor death because it found the builds 18 already existing and could not overwrite. {panel:title=Error}java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\build.pii.A.trunk\promotions\STEP 1 - Promote to DEV\builds\18 already existed; will not overwrite with build.pii.A.trunk/promotion/STEP 1 - Promote to DEV #18 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){panel}
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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title
Riddhi Sharma edited a comment on JENKINS-32152
Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
No, coudn't find any files named "atomic" in the jobs directory or entire jenkins directory. Using Set Next Build Number needs manual input to set the next build number, which we dont not want. This is surprising that setting up the next increment build number is jenkins core functionality where we are facing issue while using Promotions (promoted builds plugin - verison 2.19 though 2.24.1 is available. Would it be good to do the update?Also, if we look at the error messagebelow message below , the illegal state exception is happening and build executor are getting dead when SEVERE: Unexpected executor death because it found the builds 18 already existing and could not overwrite. {panel:title=Error}java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\build.pii.A.trunk\promotions\STEP 1 - Promote to DEV\builds\18 already existed; will not overwrite with build.pii.A.trunk/promotion/STEP 1 - Promote to DEV #18 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){panel}
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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma commented on JENKINS-32152 Re: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) No, coudn't find any files named "atomic" in the jobs directory or entire jenkins directory. Using Set Next Build Number needs manual input to set the next build number, which we dont not want. This is surprising that setting up the next increment build number is jenkins core functionality where we are facing issue while using Promotions (promoted builds plugin - verison 2.19 though 2.24.1 is available. Would it be good to do the update? Also, if we look at the error messagebelow, the illegal state exception is happening and build executor are getting dead when SEVERE: Unexpected executor death because it found the builds 18 already existing and could not overwrite. Error java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\build.pii.A.trunk\promotions\STEP 1 - Promote to DEV\builds\18 already existed; will not overwrite with build.pii.A.trunk/promotion/STEP 1 - Promote to DEV #18 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) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-32152) at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 at hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Summary: at hudson.model.RunMap.put(RunMap.java:188) - 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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Priority: Critical Blocker 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.
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Summary: java.lang.IllegalStateException: Jenkinsat Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188) 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.
[JIRA] [core] (JENKINS-32152) at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 at hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Priority: Blocker Critical 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.
[JIRA] [core] (JENKINS-32152) at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 at hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Jenkins ver. 1.642This 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] #405at 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. Previous thread 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. Add Comment This message was sent by
[JIRA] [core] (JENKINS-32152) at hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 at hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Jenkins ver. 1.642 These 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] #405at 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.Previous thread: 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. Add Comment This message was
[JIRA] [core] (JENKINS-32152) java.lang.IllegalStateException: Jenkinsat hudson.model.RunMap.put(RunMap.java:188)
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 java.lang.IllegalStateException: Jenkinsat hudson.model.RunMap.put(RunMap.java:188) Change By: Riddhi Sharma Summary: at java.lang.IllegalStateException: Jenkinsat hudson.model.RunMap.put(RunMap.java:188) 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.
[JIRA] [core] (JENKINS-32152) at hudson.model.RunMap.put(RunMap.java:188) -
Title: Message Title Riddhi Sharma created an issue Jenkins / JENKINS-32152 at hudson.model.RunMap.put(RunMap.java:188) - Issue Type: Bug Assignee: Unassigned Attachments: Dead Executor.png Components: core Created: 21/Dec/15 7:55 AM Environment: Jenkins ver. 1.642, Windows Server 2008 R2 Standard Priority: Minor Reporter: Riddhi Sharma Jenkins ver. 1.642 These 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 sub 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
[JIRA] [core] (JENKINS-32152) at hudson.model.RunMap.put(RunMap.java:188) -
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 at hudson.model.RunMap.put(RunMap.java:188) - Change By: Riddhi Sharma Jenkins ver. 1.642These 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 sub 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] #405at 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.Previous thread: 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. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-32152) at hudson.model.RunMap.put(RunMap.java:188) -
Title: Message Title Riddhi Sharma updated an issue Jenkins / JENKINS-32152 at hudson.model.RunMap.put(RunMap.java:188) - Change By: Riddhi Sharma Priority: Minor Blocker 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.
