From: Blezek, Daniel J (CRD) <blezek@cr...> - 2002-01-14 13:42:27
The intention of continuous builds in Dart is just that: to be continuously done, if they need to
be. I have a short Tcl script that I use to test if there is anything that needs to be built (cvs -n
update), and then kicks off a build. I'm planning to apply this to VXL as well as VTK, perhaps even
checking it into Dart. It's Unix specific though.
P.S. As soon as I get the logistics worked out, I'll be adding an Irix, Solaris, and Linux Nightly
and Continuous builds to the dashboard.
> -----Original Message-----
> From: Amitha Perera [mailto:perera@...]
> Sent: Friday, January 11, 2002 5:40 PM
> To: vxl-maintainers@...
> Subject: [Vxl-maintainers] Continuous builds
> Hi all
> As you gathered by the email, I've set up the dashboard to
> automatically send email when a continuous build has an
> error. Currently it is being sent to vxl-maintainers. Should we create
> a new list for this? My feeling is that we do not.
> A question: how often should continuous builds be run? Of course it,
> depends on the resources of the people running the builds, but we
> should establish a window. The dashboard is updated once an hour, so I
> think that is a good maximum frequency. Less often than every four
> hours may defeat the purpose of a "continuous" build.
> Another thing to keep in mind if a commit causes a bug, a continuous
> build will send an email. If the bug is not fixed, and someone else
> updates some other part of the source and commits, the next continuous
> run will email the someone else about the previous error. Probably not
> too serious an issue, I guess, since the person can simply look at the
> build log and realise the fault is not his.
> Vxl-maintainers mailing list
From: Wheeler, Fred (CRD) <wheeler@cr...> - 2002-01-14 16:06:00
Perhaps a new mailing list at SourceForge should be make just for this, vxl-break-monitor might be a
From: Amitha Perera [mailto:perera@...]
Sent: Monday, January 14, 2002 10:55 AM
To: William A. Hoffman
Cc: ian.m.scott@...; Vxl-maintainers (E-mail)
Subject: Re: [Vxl-maintainers] Continuous builds
I'm persuaded that the messages shouldn't go to vxl-maintainers. Is it
worth going to vxl-commits? It may be useful to know when the build
for your platform breaks, for example, but assuming the perpetrator
fixes the problem (or tells the rest of us that there is a problem), I
guess there is no real need to everyone to be immediately notified.
I've set CONTINUOUS_MONITOR_LIST to "" in (root)/DartConfig.cmake. I
guess it can stay that way until we get a need for change.
Vxl-maintainers mailing list