On Fri, Sep 28, 2012 at 10:43:44PM +0100, Neil Bowers wrote: > I was wondering if there's a way to just do test builds of dev releases. > http://wiki.cpantesters.org/wiki/SmokeTools didn't seem to have anything. I > use cpan to install modules, and reading the doc discovered the -t switch, to > run "make test". > > So out of curiosity, really, while watching TV tonight I wondered if I could > hack up a quick auto tester of dev releases. My first cut works fairly well, > and just does the following. First I reconfigured cpan to not prompt for > CPAN::Reporter, then my script does: > > - get a list of recent releases (started with search.cpan.org/recent, but now > discovered the RECENT-1d.json and friends, so will switch to that if I > continue) > - look for dev releases, only taking the most recent one > - run "cpan -t <author-path-to-dist>" > - I store things that I've seen in a DBM::Deep, so I don't try things more > than once.
You're pretty much doing the same as what I do, although I don't restrict myself to just dev releases. > Is there already something out there that does this? I don't really want to > setup a CPAN mirror, I just want a low-tech way to do some automatic testing > of dev releases via cron or launchd. > Are there any gotchas lurking for me here? Not really, other than the usual ones that come from downloading and running random code off the interweb. I mitigate the potential problems that causes by using a dedicated VM, and by periodically blowing away the perl that I've been using and reinitialising it with a clean build from a tar ball. One day I really should get round to sharing my scripts ... -- David Cantrell | semi-evolved ape-thing You may now start misinterpreting what I just wrote, and attacking that misinterpretation.
