We ran into the same problem under what sounds like the same circumstances a few years back. We initially configured thinBackup with the *Wait until...* switch turned on and had no issues for a very long time.
And then we wound up in the trap you describe. I dug around and realized certain of our long-running nightly jobs were running longer and longer, and more job were introduced, delaying thinBackup's opportunity to seize a quiet period. By the time late morning rolled around it was in the shutdown preparation mode, so I'd manually clear it, and then a delayed build would fire, and then back to shutdown prep mode, etc. So while it's possible for the thinBackup config to remain the same but build mix + timing to cause this problem. On Monday, November 27, 2017 at 9:22:37 AM UTC-8, Steve K wrote: > > > Thank you Victor Martinez and [email protected] for your great > ideas. I apologize for my late response. We were on a Thanksgiving > holiday. > > We managed to work past the problem. No Groovy scripts were to blame. > As a guess, we de-selected "Wait until Jenkins/Hudson is idle to perform a > backup" in our thinBackup settings. > That fixed the problem. > As I originally noted, however, it is very odd that we just experienced > this issue. The configuration for thinBackup had not been changed in > several months. > > -- 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/e736bc8f-23e7-4b55-9b91-9c4f97344eb3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
