2009/7/25 Craig A. Berry <craigbe...@mac.com>: > > On Jul 24, 2009, at 3:40 PM, Nicholas Clark wrote: > >> On Fri, Jul 24, 2009 at 03:35:33PM -0500, Craig A. Berry wrote: >>> >>> I've finally got Test::Smoke mostly working on VMS except for my local >>> mail configuration, thus the manual attachment here. It shows the >> >> Ooh. ooh. ooh. ooh. >> >> What will it take to get the "mail" bit sorted, so that it can run >> automatically? And run automatically on blead too? > > > I've run it successfully with both blead and maint, and I've implemented > support in Test::Smoke for the native VMS mail utility and successfully sent > myself smoke reports with it. One approach to getting mail to places it > needs to go would be to subscribe to one or another perl.org mailing list > with the account on each machine that will be generating smoke reports > (these are on my home network and I don't normally use them for e-mail). > Another approach would be to add support to Test::Smoke to use MIME::Lite's > authentication features and send via an external smtp server, though that > would involve leaving a password sitting around in clear text. Bram has now > suggested a third possibility, which is interesting. I will now go and read > the Test::Smoke FAQ and find out what I'm supposed to be doing :-). > > Oh, and you used the word "automatically," which still needs some work. I'm > currently running rsync on Mac OS X in order to get the .patch file so we > know what we're smoking, then generating a zipball and moving it to ~/Sites, > then kicking off a job on the VMS side that uses curl to pull it across and > run the smoke test. When a tuit or two present themselves, there are lots > of different approaches to coordinating and automating all of this.
Ill figure out a solution to preroll a zip snapshot on the perl5 host. Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
