CI and generation of technical reports site

[Felix Knecht <fe...@otego.com>]

Hi

There's a small issue when having a maven command like 'mvn clean 
install site' on the CI server: If there are failing test cases the site 
will never be generated and the surefire-report will never show failing 
test cases ...
Vice versa (mvn clean site install) will work for the report generation, 
but the install will never be run and failing test cases are only 
visible in the surefire report but are not indicated by a mail to the 
dev list 'Build failed in Jenkins...'.

I suggest to have 2 different jobs run: one for the technical reports 
site generation (mvn clean site -Psite-reports) and one for build of the 
artifacts (either mvn clean install or mvn clean deploy, I don't know 
which one is needed as I've found both in existing configurations).

I made a sample job setup for the jdkim project this very early morning 
(let's see if it runs). Build should fail, as there are failing test 
cases, but technical reports generation should work. Jobs are 
'jdkim-trunk' and 'jdkim-trunk-site'.

I'll setup up such *-site jobs for all the jobs building project trunks 
if ok.

WDOT?

Thanks and regards
Felix

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: CI and generation of technical reports site

[Eric Charles <er...@apache.org>]

Hi Felix,
Two  separate jobs sounds good to me.
'mvn clean deploy' (not only install) is better because we want 
snapshots in the maven repo.
Tks,
- Eric

On 16/03/2011 01:14, Felix Knecht wrote:
> Hi
>
> There's a small issue when having a maven command like 'mvn clean 
> install site' on the CI server: If there are failing test cases the 
> site will never be generated and the surefire-report will never show 
> failing test cases ...
> Vice versa (mvn clean site install) will work for the report 
> generation, but the install will never be run and failing test cases 
> are only visible in the surefire report but are not indicated by a 
> mail to the dev list 'Build failed in Jenkins...'.
>
> I suggest to have 2 different jobs run: one for the technical reports 
> site generation (mvn clean site -Psite-reports) and one for build of 
> the artifacts (either mvn clean install or mvn clean deploy, I don't 
> know which one is needed as I've found both in existing configurations).
>
> I made a sample job setup for the jdkim project this very early 
> morning (let's see if it runs). Build should fail, as there are 
> failing test cases, but technical reports generation should work. Jobs 
> are 'jdkim-trunk' and 'jdkim-trunk-site'.
>
> I'll setup up such *-site jobs for all the jobs building project 
> trunks if ok.
>
> WDOT?
>
> Thanks and regards
> Felix
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org