Date: Tue, 3 Sep 1996 16:28:19 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: terry@lambert.org, michaelh@cet.co.jp, kimc@w8hd.org, current@FreeBSD.org Subject: Re: Latest Current build failure Message-ID: <199609032328.QAA05327@phaeton.artisoft.com> In-Reply-To: <10757.841792371@time.cdrom.com> from "Jordan K. Hubbard" at Sep 3, 96 04:12:51 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > I think a more reasonable, one machine, version would be: > > > > 1) wait some interval > > 2) copy active cvs tree to static cvs tree > > 3) test-build static cvs tree > > 4) if test-build fails, go to 1 > > 5) copy successfully test-built static cvs tree to distribution > > cvs tree > > 6) people download distribution cvs tree > > That's assuming that you want to make one box both the build and the > central distribution server, and that machine definitely isn't > freefall.freebsd.org. Finding a new central distribution server > would be too much perturberation. Actually, you could seperate the process using a covert channel for the checkout for the build server: 2) copy active cvs tree on repository to statis cvs tree on build server 5) copy successfully test-built static cvs tree on build server to distribution cvs tree on distribution server (could be the same machine, the repository, or could be a third machine) Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609032328.QAA05327>