Hi Andreas,
On Fri, 08 Nov 2013 11:48:26 +0100
Andreas Schwab
Stefan Botter
writes: The second: if my observation is correct, can there be a mechanism, which "self-heals" the system?
I think obs_admin --deep-check-project can fix that up.
Indeed, it does for that particular project. That would mean, I need to set up a watcher, which monitors the log file of the scheduler and invent a logic to recheck the project. Of course this will happen more often on a remote appliance than on the central build server, where there are check-ins every few seconds, but still it seems awkward, that the scheduler, which at least detects the problem with a project, just abandons this project, and never revisits it on its own. Can the scheduler upon detecting "bad config" initiate a job to deep-check the particular project?
Andreas.
Stefan -- Stefan Botter Network Manager Jacobs University Bremen gGmbH Campus Ring 1 | 28759 Bremen | Germany Commercial registry: Amtsgericht Bremen, HRB 18117 President & Geschäftsführer: Prof. Dr. Heinz-Otto Peitgen Provost & Geschäftsführerin: Prof. Dr.-Ing. Katja Windt Chair Board of Governors: Prof. Dr. Karin Lochte