What happens is that the program scans for any Tinderbox failures, and if it finds one, then pulls the svn log history for all revisions from the point of failure back to the last successful build.
Anyone in that list is considered to be "on hook" and will receive the email. Included in the email are links to each revision and also instructions on what needs to be done.
The emails will be coming from [EMAIL PROTECTED] - so please whitelist that user or keep an eye out for them in your spam folders :)
I've tested it locally and against live Tinderbox data but that doesn't mean it won't need tweaking - please let me know if anyone sees any issues.
thanks, --- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
