[JIRA] [core] (JENKINS-33794) nextBuildNumber not updated when reload configuration
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-33794 nextBuildNumber not updated when reload configuration Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate 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-33794) nextBuildNumber not updated when reload configuration
Title: Message Title Jeff Miller commented on JENKINS-33794 Re: nextBuildNumber not updated when reload configuration Further investigation it appears, that when a job has pending builds, and a reload is done the hudson.model.Run object in the pending build queue, points back to the hudson.model.Job object. When a reload is done, a new hudson.model.Job is created and that is used for new builds. This results in a build number being used that is a duplicate of the the builds that were in the pending build queue when the reload was done. The hudson.model.Job needs to have a reload, where it will update correctly including the nextBuildNumber, to provide the hudson.model.Run objects in the pending build queue a valid object to point back to. 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-33794) nextBuildNumber not updated when reload configuration
Title: Message Title Jeff Miller commented on JENKINS-33794 Re: nextBuildNumber not updated when reload configuration FYI - this is reproduced with a clean 1.642.3 Install on Red Hat with NO additional plugins, and No changes in the plugins. 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-33794) nextBuildNumber not updated when reload configuration
Title: Message Title Jesse Glick commented on JENKINS-33794 Re: nextBuildNumber not updated when reload configuration Duplicate of something already filed. 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-33794) nextBuildNumber not updated when reload configuration
Title: Message Title Jeff Miller created an issue Jenkins / JENKINS-33794 nextBuildNumber not updated when reload configuration Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/24 8:42 PM Environment: Red Hat 7, Jenkins 1.642.2, 1.642.3 1.654 Labels: exception nextFileNumber queue core Priority: Blocker Reporter: Jeff Miller Steps to Reproduce: 1) Create a Freestyle Job. Add a "sleep 120" command to the job. 2) Execute the Freestyle Job twice. One instance will execute, the other instance will be in the queue. 3) While first instance is executing issue "Reload From Disk Command" either via Browser, CLI, or Manage Jenkins Menu 4) Wait till both instances complete execution. 5) Execute the Freestyle Job once more At this point you will receive a Dead Thread, with the following: java.lang.IllegalStateException: /var/lib/jenkins/jobs/Long Run Job/builds/2 already existed; will not overwrite with Long Run Job #2 at
