Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Ganymede builds broken for 3 nights

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

I agree. Why not send a note to this list when there's a failure for
"other" ? Sure, you'd have more people than need to looking at the
problem, but that's better than NO ONE looking at it. ;-) Or, to put
it another way, let this list be your backup when you're OOO. (Also,
by spamming the list, there's accountability because the list is
digested into the mailing list archives.)

> 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.
> Do you have a script for doing that?

Simple solution: run a build every 6 hours instead of every 24. More
builds = more chances to break/be notified/be fixed/verify fix.

Complex solution: use a modified version of my Search CVS crontab
tools to poll cvs at intervals and check if a build is warranted. If
nothing has changed, don't build. If it has, build.

I've loaded the Ganymede site contribs project into our database, so
it can be queried here:

Now, all you need to do is set up a crontab script to wget a URL like
this one every day, for daily checks. Note the "&totalonly" suffix
makes the query return just a count of changes, not the HTML of those

If you want smaller ranges than "in the last 24hrs" use the &totalonly
suffix with a query like these:

And, if you find the data's not current, you can queue a refresh like
this, then wait a few minutes before checking searchcvs.php:

Does that help? ;-)


Back to the top