Re: [cross-project-issues-dev] Ganymede builds broken for 3 nights

[David M Williams <david_williams@xxxxxxxxxx>]

From:	Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	02/17/2008 06:51 PM
Subject:	Re: [cross-project-issues-dev] Ganymede builds broken for 3 nights

---

> David,
> What can I do to prove to you that the mail-on-fail notification 
> works? The eclipse.org servers are sending the emails - I've got 
> logs to prove it...
> 

Ok, Ok, I believe you ... uh, except you _just said_
it didn't always work. :) 

"BIRT & CDT have not been receiving emails
because the system did not detect that they were the cause. It's only so
good and the "digest cannot be parsed" errors are not one of
the things that it can detect."

But, I think you are saying CDT _was_ receiving notices
for this case I mentioned, that 'development' was misspelled (i.e. there
was no "C and C++ development" category, and they just didn't
respond for 3 days (and still haven't, since I had to fix it). 

So, let me address one question more specifically.
 Vivian Kong
and Doug Schaefer ... is there some
general problem we should all address or help solve? Or ... were you too
out of the office, with no backup? 

Let me know if I (or we) can help in any
way ... I'm really not trying to blame any one, just come up with constructive
improvements. 

One constructive suggestion I've heard
is 

1) notify everyone who's made a change
upon failure (not just the detected project). 

1b) as far as I am concerned, you can
notify everyone in the .sc files when there's a failure!

Some more I'll add

2) individuals should have a "backup"
when they will be a way for a bit. (Let me know if I can help, Bjorn ...
a little :)
 
3) I'd suggest that a build be done when
ever a change is checked in ... instead of once every 24 hours ... this
way we can sometimes detect 2, 3, or 4 errors within a day, instead of
having to wait for 2, 3, or 4 days. 

4) people should remember to test their
own update site they are providing as input ... this will often defect
"digest can not be parsed" type errors. 

Hope these help, any others?