Hi!  I was lucky enough to be able to restore from a backup and a disk
failure, but now *some* of my jobs are misnumbered . . .  one job has:
$ ls -l builds/
total 16
drwxr-xr-x. 2 jenkins jenkins 4096 Nov 11 17:54 1304
drwxr-xr-x. 3 jenkins jenkins 4096 Nov 12 09:33 1305
drwxr-xr-x. 2 jenkins jenkins 4096 Nov 11 17:54 922
lrwxrwxrwx. 1 jenkins jenkins    4 Nov 12 11:44 lastFailedBuild -> 1305
lrwxrwxrwx. 1 jenkins jenkins    4 Nov 12 11:44 lastStableBuild -> 1304
lrwxrwxrwx. 1 jenkins jenkins    4 Nov 12 11:44 lastSuccessfulBuild -> 1304
lrwxrwxrwx. 1 jenkins jenkins    2 Nov 12 11:44 lastUnstableBuild -> -1
lrwxrwxrwx. 1 jenkins jenkins    4 Nov 12 11:44 lastUnsuccessfulBuild ->
1305
-rw-r--r--. 1 jenkins jenkins 2772 Nov 11 17:54 legacyIds

and:
$ cat nextBuildNumber
936

When I try to run this job I get:
SEVERE: Unexpected executor death
java.lang.IllegalStateException: cannot create a build with number 937
since that (or higher) is already in use among [922, 1304, 1305]

I've tried to set the # in nextBuildNumber to 1306 but it reverts back to
930-something  . . .

Any ideas?

Thanks a lot,
Guy

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CABnTgtXm98PMYguF6RuDgmRhXPy2%2BqdPz66cpjWfQeSEmr9%2B8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to