We have a Jenkins project that uses the build step "Trigger builds on other projects" and is set to "Block until the triggered projects finish their builds". This project has a lot of those dependencies and runs for several hours total (3 to 5). Sometimes the thinBackup kicks right in in the middle and puts Jenkins into Shutdown mode. In this case the main project is still active because it is blocked by the other triggered projects. And because Jenkins is in shutdown mode, it won't start building those; they stay in the queue. And the thinBackup client doesn't run either. Maybe because the Main Project is still active? (just an assumption). At this stage we have a deadlock. Nothing is going to build anymore, the backup is not happening and Jenkins won't come out of Shutdown mode. If I cancel the shutdown mode, one of the queued up projects starts to build, but shortly after that the shutdown mode will be re-enabled by the thinBackup plugin. You can see that in the log. The only way to get out of this state is to repeatedly cancel the shutdown until all queued projects finished building. Then the thinBackup plugin backs things up and takes Jenkins out of shutdown mode.

Could someone please take a look? I have the Jenkins error log attached.

Thanks,
Sandra