[Webtest] [dev] build re-animated

[Denis N. Antonioli]

Hi everybody

On Tue, 18 Jan 2005, Dierk Koenig wrote:

> The build is working again,

Hoorah! I truly realized during this last weeks how accustomed
I've grown to continuous inegration :-)

> Build time is still much too long (20 mins) while it runs
> in 3 mins on my laptop. Reading through
> the xml logs suggests that the delay is distributed evenly
> over the tasks. 
> 
> I think about introducing a flag to distinguish between a full
> and a minor build. Minor builds could compile incrementally and
> skip some tasks like clover, checkstyle, apidoc, manuals? and
> skip some of the selftests (pdf?, applet?, groovy?).
> Full builds on the buildserver could be run on an own schedule
> (nightly?, force manually?).
> Developers would still be obliged to run the full build locally
> before any commit.
> 
> Any options on this?

I don't know how much faster it would get, but I see a point for
minor build with plain compile and the complete test suite, and
major build with everyting.

If a minor build has to skip some tests, I'd distribute the tests
to skip over all webtest. I'm afraid that skipping complete parts
(such as pdf, applet or groovy) would hide errors in these parts
that results from changes at another place.

>From the trouble we had in the last time, using more threads is
not an option, is it?

There is a well known quote to the tune of 'one can measure the
degree of a civilization by its level of automation'. A major build
shouldn't be manual. Either nightly, or every five successful minor
builds, or ... 


Happy Testing
	dna