Re: smoking VMS (was Re: maint-5.10 status on VMS)

Craig A. Berry wrote:
> 
> 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.

I can supply you with a GIT program that can clone a repository.  I can 
not get the other functions working for a while due to limitations in 
the GNV ports of several utilities and some other problems.

If you (or anyone else) wishes to pursue that, drop a mail on the 
vms-perl list and I will respond with the details.

I do not know if the clone function can pull down a specific branch.
It is also pretty slow.  It takes at least 1/2 for the git clone to pull 
down Perl on my DS-10.

-John
[email protected]
Personal Opinion Only