comment on

Good stuff! Now all I need to do is convince my lab to install SVN so that I can play around with it....

One thing you might consider is sending the email only on failure; successful builds succeed quietly. I've played around with a few "email-a-day" scripts (mostly of my own devising), and I find that even at such a low frequency, after a few weeks of the same (or similar) messages I tend to delete them unread. Parsing the tests' output might be more effort than it's worth; can you simply assume that the build succeeded if $stderr is empty?

Shameless self-promotion: there's a good discussion of when to log and notify in the replies to Defensive Programming and Audit Trails.

-- F o x t r o t U n i f o r m Found a typo in this node? /msg me % man 3 strfry

In reply to Re: Automated module testing with SVN::Client and Module::Build by FoxtrotUniform
in thread Automated module testing with SVN::Client and Module::Build by sintadil

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks