[JIRA] [core] (JENKINS-23130) nextBuildNumber keeps being set to previous numbers

Wed, 21 May 2014 11:37:23 -0700

So this looks like it is caused by two things:

One, updateNextBuildNumber() is called with a too-low value. I'm not sure why this happens, yet.

Two, updateNextBuildNumber() has a sanity check that fails if Jenkins doesn't know about all the builds on disk (as in JENKINS-15156).

Jobs.java
public synchronized void updateNextBuildNumber(int next) throws IOException {
        RunT lb = getLastBuild();
        if (lb!=null ?  next>lb.getNumber() : next>0) {
            this.nextBuildNumber = next;
            saveNextBuildNumber();
        }
    }


This check is only as good as the information in getLastBuild(). If the Job was unable to load everything from disk, then this number will be artificially low.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/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.

Reply via email to