Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-27530] nextBuildNumber snafu after reload #2439

Merged
merged 1 commit into from
Jul 8, 2016

Conversation

jglick
Copy link
Member

@jglick jglick commented Jul 8, 2016

JENKINS-27530

Only purports to address the issue of reloading Jenkins while there are builds waiting in the queue. An apparent MatrixConfiguration bug will be investigated separately.

@reviewbybees

…sure that every Queue.Item.task corresponds to a live Job, lest nextBuildNumber be bogus.
this.nextBuildNumber = Collections.max(foldersInt) + 1;
RunT lB = getLastBuild();
synchronized (this) {
this.nextBuildNumber = lB != null ? lB.getNumber() + 1 : 1;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could leave the original implementation of JENKINS-11563 untouched for a non-LazyLoadingJob, but may as well use this simpler implementation.

@ghost
Copy link

ghost commented Jul 8, 2016

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@jtnord
Copy link
Member

jtnord commented Jul 8, 2016

🐝

@svanoort
Copy link
Member

svanoort commented Jul 8, 2016

🐝 and 🎉 for including some cleanup and defensive cases for other possibilities.

@stephenc
Copy link
Member

stephenc commented Jul 8, 2016

🐝

@jglick jglick merged commit 3ef1db5 into jenkinsci:master Jul 8, 2016
@jglick jglick deleted the nextBuildNumber-JENKINS-27530 branch July 8, 2016 22:51
jglick added a commit that referenced this pull request Jul 8, 2016
oleg-nenashev pushed a commit that referenced this pull request Jul 15, 2016
…uild.] (#2444)

* Fixed JENKINS-33201 [Java JSON exception with an empty parametrized
build.]

* FIXED JENKINS-33201. Changed to FormException instead of Failure

* That fix was never in a released version.

So it cannot have been reverted.

* Lowercase i for consistency

* Remove the concept of yanking dead executors.

* Another unnecessary call to doYank.

* [FIXED JENKINS-27530] Jenkins.reload must also reload the Queue to ensure that every Queue.Item.task corresponds to a live Job, lest nextBuildNumber be bogus.

* [JENKINS-27530] Noting #2439 & #2440.

* FIXED JENKINS-33201. Changed to FormException instead of Failure

* [FIXED JENKINS-33201 .FormException is thrown if parameterDefinitions are not available .

* Changing one more Tab to Space

* Moved checkForEmptyParameters to Job class
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants