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
Thank you Victor Martinez and matthew...@diamond.ac.uk 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
If anyone can run any system groovy script then they might easily run the
'safe-restart'. can you confirm whether the script security is
enabled? https://jenkins.io/doc/book/managing/script-approval/
--
You received this message because you are subscribed to the Google Groups
"Jenkins
Anything in the logs?
Did anyone install
https://wiki.jenkins.io/display/JENKINS/Post-initialization+script?
Matthew
--
This e-mail and any attachments may contain confidential, copyright and or
privileged material, and are for the use of the intended addressee only. If you
are not the
