Building Maven site prevents Hudson build report plugins?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Building Maven site prevents Hudson build report plugins?

Eric Lewis
Hi

We build our projects using a number of plugins (Checkstyle, PMD etc.), which works fine for CI.
However, we also have a nightly build which creates a Maven site for every project.

At that point, the Hudson graph always shows zero results (since we upgraded to 1.362). The Maven build command is that same, except for site building:

CI: [clean, package, findbugs:findbugs, pmd:pmd, pmd:cpd, checkstyle:checkstyle]

Nightly build: [site-deploy, clean, package, findbugs:findbugs, pmd:pmd, pmd:cpd, checkstyle:checkstyle]

However, Maven shows a different output:

CI:
[FINDBUGS] Successfully parsed file /ige/hudson/work/jobs/ip/workspace/ip-apm/target/findbugsXml.xml of module Application Programming Module of Intellectual Property Services with 0 warnings.
[INFO] [pmd:pmd {execution: default-cli}]
[PMD] Successfully parsed file /ige/hudson/work/jobs/ip/workspace/ip-apm/target/pmd.xml of module Application Programming Module of Intellectual Property Services with 0 warnings.
[INFO] [pmd:cpd {execution: default-cli}]
[DRY] Successfully parsed file /ige/hudson/work/jobs/ip/workspace/ip-apm/target/cpd.xml of module Application Programming Module of Intellectual Property Services with 2 warnings.
[INFO] [checkstyle:checkstyle {execution: default-cli}]
[CHECKSTYLE] Successfully parsed file /ige/hudson/work/jobs/ip/workspace/ip-apm/target/checkstyle-result.xml of module Application Programming Module of Intellectual Property Services with 0 warnings.

Nightly build:
[FINDBUGS] Skipping maven reporter: there is already a result available.
[INFO] [pmd:pmd {execution: default-cli}]
[PMD] Skipping maven reporter: there is already a result available.[INFO] [pmd:cpd {execution: default-cli}]
[DRY] Skipping maven reporter: there is already a result available.
[INFO] [checkstyle:checkstyle {execution: default-cli}]
[CHECKSTYLE] Skipping maven reporter: there is already a result available.

Any idea what's going on?

Best regards,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Building Maven site prevents Hudson build report plugins?

domi@fortysix.ch
Eric,

I would say your phase ordering in the command is wrong for the nightly build:
[site-deploy, clean, package, findbugs:findbugs, pmd:pmd, pmd:cpd,  
checkstyle:checkstyle]

This way you build and deploy your site befor you actualy anaylysed  
your project. I think 'site-deploy' should be the last step you call.

regards Domi



Zitat von "Lewis, Eric" <[hidden email]>:

> Hi
>
> We build our projects using a number of plugins (Checkstyle, PMD  
> etc.), which works fine for CI.
> However, we also have a nightly build which creates a Maven site for  
> every project.
>
> At that point, the Hudson graph always shows zero results (since we  
> upgraded to 1.362). The Maven build command is that same, except for  
> site building:
>
> CI: [clean, package, findbugs:findbugs, pmd:pmd, pmd:cpd,  
> checkstyle:checkstyle]
>
> Nightly build: [site-deploy, clean, package, findbugs:findbugs,  
> pmd:pmd, pmd:cpd, checkstyle:checkstyle]
>
> However, Maven shows a different output:
>
> CI:
> [FINDBUGS] Successfully parsed file  
> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/findbugsXml.xml of  
> module Application Programming Module of Intellectual Property  
> Services with 0 warnings.
> [INFO] [pmd:pmd {execution: default-cli}]
> [PMD] Successfully parsed file  
> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/pmd.xml of module  
> Application Programming Module of Intellectual Property Services  
> with 0 warnings.
> [INFO] [pmd:cpd {execution: default-cli}]
> [DRY] Successfully parsed file  
> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/cpd.xml of module  
> Application Programming Module of Intellectual Property Services  
> with 2 warnings.
> [INFO] [checkstyle:checkstyle {execution: default-cli}]
> [CHECKSTYLE] Successfully parsed file  
> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/checkstyle-result.xml of  
> module Application Programming Module of Intellectual Property  
> Services with 0 warnings.
>
> Nightly build:
> [FINDBUGS] Skipping maven reporter: there is already a result available.
> [INFO] [pmd:pmd {execution: default-cli}]
> [PMD] Skipping maven reporter: there is already a result  
> available.[INFO] [pmd:cpd {execution: default-cli}]
> [DRY] Skipping maven reporter: there is already a result available.
> [INFO] [checkstyle:checkstyle {execution: default-cli}]
> [CHECKSTYLE] Skipping maven reporter: there is already a result available.
>
> Any idea what's going on?
>
> Best regards,
> Eric
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

AW: Building Maven site prevents Hudson build report plugins?

Eric Lewis
Hi Domi

Logically speaking: yes.
However, we change the job's configuration before the nightly build using a shell script, and the easiest is to add and delete at the beginning.
It's always worked, so I'm not sure if the sequence of the goals matters for Maven. I'll ask that on the Maven mailing list.

Best regards,
Eric

-----Urspr√ľngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]]
Gesendet: Montag, 19. Juli 2010 20:00
An: [hidden email]
Betreff: Re: Building Maven site prevents Hudson build report plugins?

Eric,

I would say your phase ordering in the command is wrong for the nightly build:
[site-deploy, clean, package, findbugs:findbugs, pmd:pmd, pmd:cpd,  
checkstyle:checkstyle]

This way you build and deploy your site befor you actualy anaylysed  
your project. I think 'site-deploy' should be the last step you call.

regards Domi



Zitat von "Lewis, Eric" <[hidden email]>:

> Hi
>
> We build our projects using a number of plugins (Checkstyle, PMD  
> etc.), which works fine for CI.
> However, we also have a nightly build which creates a Maven site for  
> every project.
>
> At that point, the Hudson graph always shows zero results (since we  
> upgraded to 1.362). The Maven build command is that same, except for  
> site building:
>
> CI: [clean, package, findbugs:findbugs, pmd:pmd, pmd:cpd,  
> checkstyle:checkstyle]
>
> Nightly build: [site-deploy, clean, package, findbugs:findbugs,  
> pmd:pmd, pmd:cpd, checkstyle:checkstyle]
>
> However, Maven shows a different output:
>
> CI:
> [FINDBUGS] Successfully parsed file  
> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/findbugsXml.xml of  
> module Application Programming Module of Intellectual Property  
> Services with 0 warnings.
> [INFO] [pmd:pmd {execution: default-cli}]
> [PMD] Successfully parsed file  
> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/pmd.xml of module  
> Application Programming Module of Intellectual Property Services  
> with 0 warnings.
> [INFO] [pmd:cpd {execution: default-cli}]
> [DRY] Successfully parsed file  
> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/cpd.xml of module  
> Application Programming Module of Intellectual Property Services  
> with 2 warnings.
> [INFO] [checkstyle:checkstyle {execution: default-cli}]
> [CHECKSTYLE] Successfully parsed file  
> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/checkstyle-result.xml of  
> module Application Programming Module of Intellectual Property  
> Services with 0 warnings.
>
> Nightly build:
> [FINDBUGS] Skipping maven reporter: there is already a result available.
> [INFO] [pmd:pmd {execution: default-cli}]
> [PMD] Skipping maven reporter: there is already a result  
> available.[INFO] [pmd:cpd {execution: default-cli}]
> [DRY] Skipping maven reporter: there is already a result available.
> [INFO] [checkstyle:checkstyle {execution: default-cli}]
> [CHECKSTYLE] Skipping maven reporter: there is already a result available.
>
> Any idea what's going on?
>
> Best regards,
> Eric
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: AW: Building Maven site prevents Hudson build report plugins?

domi@fortysix.ch
Eric,

it does matter.
You can do an easy test your self, execute this:

$> mvn clean package
Output:
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: /private/tmp/test/dude/target/dude-1.0-SNAPSHOT.jar
[INFO]  
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL

$> mvn package clean
Output:
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory /private/tmp/test/dude/target
[INFO]  
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL

You see that in the first execution the JAR got build on the last  
line, where with the later command the last line deletes some files.

I think you'r mixing things up: what maven knows about, is that if you  
want to execute 'install', it has to go through some steps (lifecycle  
phases) like copy-resuorce, compile, test... in advance. But if you  
tell it to execute two lifecycle phases in one execution, it will just  
do the same twice. In your case it's not even only lifecycle phases -  
but also plugin goals (e.g. "pmd:pmd") these are not automaticly  
triggering any lifecycle phases in advance (well, it actualy depends  
on the plugin/goal...)

regards Domi


Zitat von "Lewis, Eric" <[hidden email]>:

> Hi Domi
>
> Logically speaking: yes.
> However, we change the job's configuration before the nightly build  
> using a shell script, and the easiest is to add and delete at the  
> beginning.
> It's always worked, so I'm not sure if the sequence of the goals  
> matters for Maven. I'll ask that on the Maven mailing list.
>
> Best regards,
> Eric
>
> -----Urspr√ľngliche Nachricht-----
> Von: [hidden email] [mailto:[hidden email]]
> Gesendet: Montag, 19. Juli 2010 20:00
> An: [hidden email]
> Betreff: Re: Building Maven site prevents Hudson build report plugins?
>
> Eric,
>
> I would say your phase ordering in the command is wrong for the  
> nightly build:
> [site-deploy, clean, package, findbugs:findbugs, pmd:pmd, pmd:cpd,
> checkstyle:checkstyle]
>
> This way you build and deploy your site befor you actualy anaylysed
> your project. I think 'site-deploy' should be the last step you call.
>
> regards Domi
>
>
>
> Zitat von "Lewis, Eric" <[hidden email]>:
>
>> Hi
>>
>> We build our projects using a number of plugins (Checkstyle, PMD
>> etc.), which works fine for CI.
>> However, we also have a nightly build which creates a Maven site for
>> every project.
>>
>> At that point, the Hudson graph always shows zero results (since we
>> upgraded to 1.362). The Maven build command is that same, except for
>> site building:
>>
>> CI: [clean, package, findbugs:findbugs, pmd:pmd, pmd:cpd,
>> checkstyle:checkstyle]
>>
>> Nightly build: [site-deploy, clean, package, findbugs:findbugs,
>> pmd:pmd, pmd:cpd, checkstyle:checkstyle]
>>
>> However, Maven shows a different output:
>>
>> CI:
>> [FINDBUGS] Successfully parsed file
>> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/findbugsXml.xml of
>> module Application Programming Module of Intellectual Property
>> Services with 0 warnings.
>> [INFO] [pmd:pmd {execution: default-cli}]
>> [PMD] Successfully parsed file
>> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/pmd.xml of module
>> Application Programming Module of Intellectual Property Services
>> with 0 warnings.
>> [INFO] [pmd:cpd {execution: default-cli}]
>> [DRY] Successfully parsed file
>> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/cpd.xml of module
>> Application Programming Module of Intellectual Property Services
>> with 2 warnings.
>> [INFO] [checkstyle:checkstyle {execution: default-cli}]
>> [CHECKSTYLE] Successfully parsed file
>> /ige/hudson/work/jobs/ip/workspace/ip-apm/target/checkstyle-result.xml of
>> module Application Programming Module of Intellectual Property
>> Services with 0 warnings.
>>
>> Nightly build:
>> [FINDBUGS] Skipping maven reporter: there is already a result available.
>> [INFO] [pmd:pmd {execution: default-cli}]
>> [PMD] Skipping maven reporter: there is already a result
>> available.[INFO] [pmd:cpd {execution: default-cli}]
>> [DRY] Skipping maven reporter: there is already a result available.
>> [INFO] [checkstyle:checkstyle {execution: default-cli}]
>> [CHECKSTYLE] Skipping maven reporter: there is already a result available.
>>
>> Any idea what's going on?
>>
>> Best regards,
>> Eric
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]