Re: Daily Build


"Why Tea" <ytlim1@xxxxxxxxx> wrote in message
news:1183026641.388717.98050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 28, 10:23 am, skuha...@xxxxxx wrote:
Why Tea wrote:
Has anybody attempted Daily Build (http://en.wikipedia.org/wiki/
Daily_build) with Expect or any other tools? Please share your
thoughts and experience.

I once wrote a Nightly/Continuous-Build-System using Tcl with
automatic reports (html, text, mail, compiler-output-parsing for
different platforms etc.), tests for the generated binaries and
repository links from error messages and such for a software base
containing > million loc of c++ which was sectioned in Modules. Its
multiplatform, automatically generates build rules from configure,
makefile, imakefiles, qmake-files or custom build rules and others. I
think, it was pretty complete in features, but a little bit messy,
since it growed out of something smaller. Is that what you mean?

Regards
Stephan

Hi Stephen, that's pretty much the idea. To be more specific, it's an
unattended build/link/test tool which does the following:

1) based on a makefile, check out all relevant source files from a
source control system.
2) produce binaries thru the makefile(s)
3) load the binaries into the system(s) and configure - here I'm
thinking about embedded systems
4) perform regression tests (or smoke tests?)
5) produce test results and email fault reports to designers (3 to
400)

I think what you have done was very close, except perhaps your system
is a computer system which Step 3 load/configure wasn't applicable.

I assume many designers were involved in your case, how did you
coordinate so that a "good" version of the module was always checked
in by the designer before he left the building? What was the success
rate of your nightly build? Were many faults found during the nightly
tests?

/Why Tea


I haven't tried it myself, but you might want to visit

http://public.kitware.com/Dart

--Mark


.

Relevant Pages

  • Re: Daily Build
    ... produce binaries thru the makefile ... produce test results and email fault reports to designers (3 to ... I assume many designers were involved in your case, ...
    (comp.lang.tcl)
  • Re: Daily Build
    ... I once wrote a Nightly/Continuous-Build-System using Tcl with ... automatic reports (html, text, mail, compiler-output-parsing for ...
    (comp.lang.tcl)