Re: 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

Comment on Re: Automated module testing with SVN::Client and Module::Build Download Code

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
Now all I need to do is convince my lab to install SVN so that I can play around with it.... Good luck with that. :) 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? I don't know about that, but it's a very good idea to do some investigating. With Test::More at least, using the verbose flag causes output to go to $stderr even if the tests are successful. This complicates things if you want verbose testing. Of course, there's dozens of other test modules out there, so... it may be possible to use one of those instead. Shameless self-promotion I personally don't see anything wrong with these, so long as they provide useful information.	[reply]
Re^2: Automated module testing with SVN::Client and Module::Build by stvn (Monsignor) on Sep 16, 2004 at 16:39 UTC
Good stuff! Now all I need to do is convince my lab to install SVN so that I can play around with it.... Well if they use CVS, then i suggest you do what I did. Install it on your machine first, then show/demo it to everyone who will sit still long enough to listen. I have found very few CVS users or administrators who dont immediately see the superiority of Subversion. Of course, I am in the workplace, not the university, so you may not have the same freedom to install software. However, if you really just want to play around with it, then just install it, its pretty painless (I have done it on Linux, Windows and OS X with little trouble) and you don't need a seperate server if you dont want to. -stvn	[reply]


P is for Practical
	PerlMonks