We use multiple perl scripts to do the job: one to build the C++ code, one to run the C++ white box regression tests, one (Test::Harness prove) to run the Perl white box regression tests, another to run the black box regression tests, and so on. Writing each script as a stand-alone tool has proved useful because developers can use them standalone, plus the same tool can be called from the high level nightly smoker script.

We don't do continuous builds. We do complete builds and regression tests nightly. This is mainly because we support a dozen or so different platforms from a single source code base. We use rsh to control running the nightly smoker across the many build and test machines.

In reply to Re: Pragmatic project automation by eyepopslikeamosquito
in thread Pragmatic project automation by sutch

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.