I called victory way too fast, still can happen, just not as often. The fact that the slave can flood the master is a bit annoying, it should wait and continue later. Right now the behavior is if this happen, the slave/master hang (web gui is still accessible, but impossible to cancel the jobs) and I need to restart the Jenkins daemon everyday :-(
Maybe it's impossible to have the jobs folder under a network mount where the network can sometime be under heavy usage. This was solving the split between the master config and the jobs config/results for backup purpose. The master config change at slow pace and we manually backup the whole machine when doing update keeping the 2 last in case of problems to quickly revert. Jobs on the other hand need to be backup every day in incremental way. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/45d23afd-7861-452b-b5ec-dca615d09430%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
