in reply to Automated module testing with SVN::Client and Module::Build
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
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Automated module testing with SVN::Client and Module::Build
by sintadil (Pilgrim) on Sep 15, 2004 at 18:32 UTC | |
|
Re^2: Automated module testing with SVN::Client and Module::Build
by stvn (Monsignor) on Sep 16, 2004 at 16:39 UTC |