-
Notifications
You must be signed in to change notification settings - Fork 236
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
trouble with persistence of build-numbers with backup/restore #210
Comments
Hi @pniederlag, After the restore the operator calls the Cheers |
Yes, I've spent 3 week trying to find all the workarounds to make multi-brunch work with job dls and backups... |
This is a funny bug actually, if you click run enough times it starts to work ;) |
Closing as a duplicate of #104 |
We have backup/restore integrated so whenever a fresh instance of jenkins is created we have the history of our jobs available.
Unfortunatly we can't trigger new builds though as we are running into exceptions when clicking the build buttons/links. We always first have to go to manage jenkins, reload configuration from disk, in order for jenkins to have proper build numbers in place for the build/run actions.
This ist the exception, before running "reload from disk":
Is this a general problem or just something messed up on our side?
The text was updated successfully, but these errors were encountered: