Re: Setting up Test::Smoke

[email protected] (Abe Timmerman) Sat, 2 Aug 2003 00:02:46 +0200
Newsgroups perl.daily-build
Message-ID <[email protected]>
Op een zonnige zomerdag (Friday 01 August 2003 22:57), schreef Alan Burlison:

> Abe Timmerman wrote:
> > Looking at ftp://ftp.cpan.org/pub/CPAN (which I suppose is the source for
> > your mirror) I cannot find any bleeding-edge sources there.
> >
> > Is there no way you can make the CPAN-mirror machine also rsync or mirror
> > (part of) APC? I assume that the mirror machine has internet-access.
>
> Which bits?  The machines are behind a firewall and I have had to go to
> enormous lengths to get the CPAN rsync to work even semi-reliably through
> it.

Okay, that seems like more trouble than needed since you have p4 access.
FYI: the perl-current branch can be rsynced like:

	rsync -az --delete ftp.linux.activestate.com::perl-current /your/mirror/dir/

or ftp-mirror from (there is mirror.pl on CPAN):

	ftp.linux.activestate.com/pub/staff/gsar/APC/perl-current

for maint-5.8/perl these are:
	rsync://ftp.linux.activestate.com::perl-5.8.x
	ftp://ftp.linux.activestate.com/pub/staff/gsar/APC/perl-5.8.x

for maint-5.6/perl-5.6.2 these are:
	rsync://ftp.linux.activestate.com::perl-5.6.2
	ftp://ftp.linux.activestate.com/pub/staff/gsar/APC/perl-5.6.2


I have been working on a ftp-based syncer, but that was so slow and 
unreliable, that I put it on ice.

> > You could set up the mirror machine to only "synctree.pl" (from cron) and
> > have your smoke boxen use sync_type => 'copy' (or even rsync  with two
> > local paths if that 'll work over NFS).
> >
> > If you want more info on this, just let me know.
>
> Yes, info on exactly what I need to pull would be great.  Another
> alternative is to 'p4 sync' as I have perforce access.

I don't know about p4, but if you can use that to get the branches you want to 
smoke, that sounds like the easy way.

Once you have a synced source-tree on one machine that is NFS-accessable, you 
can use that as your source for the smoke boxen.

OTOH, if the 'p4 sync' works from all boxen, it depends on the way the command 
is called whether you can 'tric' Test::Smoke into thinking you do rsync. That 
might involve a small shell script that does the p4 command and you specify 
that as your rsync binary.


good luck,

Abe
-- 
Amsterdam Perl Mongers http://amsterdam.pm.org
#! /usr/bin/perl 
tie *STDIN, JAPH => qw(Just another Perl hacker);print while <STDIN>;
sub JAPH::TIEHANDLE {$~=shift;bless \($^=join$/,@_),$~}
sub JAPH::READLINE  {$/=$^=~s/^(.+)\n?//?$1:undef;$\=$^eq""?"\n":" ";$/}