[Engine-devel] Jenkins testing of patch what do we want to check?

[Eyal Edri]

----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Robert Middleswarth" <robert at middleswarth.net>
> Cc: engine-devel at ovirt.org, "infra" <infra at ovirt.org>
> Sent: Thursday, August 9, 2012 8:37:03 AM
> Subject: Re: [Engine-devel] Jenkins testing of patch what do we want to	check?
> 
> On 08/09/2012 05:05 AM, Robert Middleswarth wrote:
> > Unlike vdsm were the entire unit test takes 2 min to process the
> > Engine
> > has several jobs many that take longer then 15 min to run. So here
> > is
> > the questions.
> >
> > What current jobs do we want to run on each patch submission?
> >
> 
> all...
> developers should verify the default unitests, or specific tests for
> areas they are touching.
> but jenkins should run the findbugs, gwt compilation and enable all
> unitests.
> 

like itamar said.
we should run every job we can to verify code with to avoid regressions and errors pre-commit.

- create/upgrade db
- checkstyle, findbugs, unit-tests, dao-tests... 
- maybe animal sniffer - to verify backward compatibility to jdk6

We can't do it with current jenkins resources, that's the main reason why
we need more slaves. 

> 
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>