Re: smoking VMS (was Re: maint-5.10 status on VMS)
On Jul 28, 2009, at 6:19 AM, demerphq wrote: 2009/7/25 demerphq demer...@gmail.com: Ill figure out a solution to preroll a zip snapshot on the perl5 host. Hi, its not producing zip files, i guess i can try that next, but you can now get .tar.gz snapshots from the web page that DO contain a more or less relevent .patch file. Excellent. Worked find for me: $ type .patch blead 2009-07-28.20:22:52 9b05e874888db731870edce844ef9f3194eafed4 GitLive-blead-1703-g9b05e87 VMS folks should note that they'll likely have better luck unpacking the tarball using the gnutar that comes with GNV than with the older vmstar utility. Craig A. Berry mailto:craigbe...@mac.com ... getting out of a sonnet is much more difficult than getting in. Brad Leithauser
Re: smoking VMS (was Re: maint-5.10 status on VMS)
On Fri, Jul 24, 2009 at 06:38:58PM -0500, John E. Malmberg wrote: Craig A. Berry wrote: 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. blead, maint-5.10 and maint-5.8 (at least) are still available via rsync. Does that help? If anyone else on the VMSperl list has the time and enthusiasm to pursue this, and get a VMS machine smoking regularly, that would be a great benefit to us non-VMS users. Nicholas Clark
Re: smoking VMS (was Re: maint-5.10 status on VMS)
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/
smoking VMS (was Re: maint-5.10 status on VMS)
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? Nicholas Clark
Re: smoking VMS (was Re: maint-5.10 status on VMS)
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. _ Craig A. Berry mailto:craigbe...@mac.com ... getting out of a sonnet is much more difficult than getting in. Brad Leithauser
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 wb8...@qsl.net Personal Opinion Only