-
Improvement
-
Resolution: Fixed
-
Major
-
None
backup was done on Debian 6.0/ amd64 / Jenkins 1.420, restore on Debian 6.0 / VMWare i386 / Jenkins 1.430 both backup and restore with thinBackup 1.4
A new build for a given project (been backuped with last version #n) will not build as version #n+1 but as build #1.
ThinBackup do not backup the nextBuildNumber (because it is in the workspace)
I propose to include in the backup the nexBuildNumber, in order to be able to restore a functional backup.
As we implement the strategy we thought that it could be a problem to backup/restore the buildnumber. A build number must be unique in any case to prevent troubles. In the case if you restore a older backuped configuration you get in the situation that you uses a number twice. So we need to secure that a number is not used twice.
Maybe the solution is to allow a backup/restore but check that the build number is greater or equal the current on. So a already used buildnumber cannot be used twice.