NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Ports & Packages infrastructure & feature import. (fwd)



At Sat, 3 Sep 2011 09:09:31 +0300,
Jukka Ruohonen wrote:
> 
> On Fri, Sep 02, 2011 at 10:15:49AM -0400, Marko Schütz Schmuck wrote:
> > It might also be a good idea to automate integration testing before
> > committing and reject failed integrations. There is an IMNSHO
> > excellent tool in Aegis (aegis.sf.net). 
> 
> I agree that (automated) "continuous integration" is a good idea. However,
> I doubt whether it scales to projects with several millions of lines of code.

There are relatively few lines that change with each change set and
there are few targets that will be impacted. The files generated from
a build prior to integration of the change are kept in the project
directory. The build tool needs to be capable of using a path (VPATH)
to search for files or alternatively the build directory can be
populated with links to the changeset's baseline. Also, not all tests
are run automatically for each changeset: the developer specifies and
submits the tests that the changeset must satisfy (and that the
previous version must fail). Of course, regression tests are also
possible and aegis can suggest regression tests based on the files in
the changeset and the tests that were run for these files in the past.

Best ragards,

Marko

Attachment: pgpbjB2Lz3Fyz.pgp
Description: PGP signature



Home | Main Index | Thread Index | Old Index