Ah, now I understand:-) You don't need to download anything, this is maven doing for you. You only need to add for each tool a corresponding section to your parent pom, here is an example: https://github.com/jenkinsci/analysis-pom-plugin/blob/master/pom.xml
(Search for check style and findbugs) Then you can start Maven with mvn checkstyle:checkstyle findbugs:findbugs Ulli Am 04.10.2012 um 12:49 schrieb Rob Withers <reefed...@gmail.com>: > Oh? I need to invoke FindBugs, and all the other analysis tools in maven? :) > I am brand new to maven and Jenkins, as an admin...if you couldn't tell... > > So how can I generate reports for all my analysis tools, or at least the > following: > 1) FindBugs > 2) PMD > 3) Checkstyle > > Ok, I downloaded these three zips and installed them, but I am at a loss for > how to configure maven to call them. I did see I want to call them on the > verify step. Do you have a good link or description on how to have maven > invoke these? > > Thanks, > Rob > > > -----Original Message----- From: Ulli Hafner > Sent: Thursday, October 04, 2012 2:40 AM > To: jenkinsci-users@googlegroups.com > Subject: Re: no code analysis showing up with my builds > > Ok, then the registration is done correctly. > > Seems that the plug-ins don't detect that the corresponding maven goal is > started. How do you invoke findbugs in maven? When started with > findbugs:findbugs then everything should work out of the box… > > Ulli > > > Am 04.10.2012 um 02:37 schrieb Rob Withers <reefed...@gmail.com>: > >> One last thing I see. I deleted the config.xml inside the modules >> subdirectory and copied the config.xml from the modules\murmur-events >> direcotory to the modules subdirectory. Then I reran the build. THe result >> did NOT have the analysis done and the config.xml in the modules >> subdirectory, after running the build, did NOT have the reporters section >> with the analysis tools. >> >> Tchuss, >> Rob >> >> -----Original Message----- From: Rob Withers >> Sent: Wednesday, October 03, 2012 7:46 PM >> To: jenkinsci-users@googlegroups.com >> Subject: Re: no code analysis showing up with my builds >> >> Oops, I just saw that I have 2 config.xml files in my project. >> >> One is here: C:\software\Jenkins\jobs\murmur-events >> >> The other is here: >> C:\software\Jenkins\jobs\murmur-events\modules\murmur-events$murmur-events >> >> The one inside the modules directory does not have the analysis reporters >> section. >> >> Rob >> >> -----Original Message----- From: Ulli Hafner >> Sent: Wednesday, October 03, 2012 5:51 PM >> To: jenkinsci-users@googlegroups.com >> Subject: Re: no code analysis showing up with my builds >> >> Is there a Findbugs action in your job's config.xml file? >> >> Ulli >> Am 03.10.2012 um 19:00 schrieb Rob Withers <reefed...@gmail.com>: >> >>> There are no logs for analysis tools in the console log. >>> >>> Rob >>> >>> -----Original Message----- From: Ulli Hafner >>> Sent: Wednesday, October 03, 2012 12:47 PM >>> To: jenkinsci-users@googlegroups.com >>> Subject: Re: no code analysis showing up with my builds >>> >>> The analysis plug-ins log their results in the console log. Is there >>> something printed out? >>> E.g. [FINDBUGS] Parsing... >>> >>> Does your build produce the artifacts (e.g. FindBugs results XML file) that >>> are read as input by the plugins? >>> >>> Ulli >>> >>> Am 03.10.2012 um 17:05 schrieb Rob Withers <reefed...@gmail.com>: >>> >>>> I have the following plugins loaded: >>>> 1) JUnit Attachments Plugin >>>> 2) Static Analysis Utilities >>>> 3) Static Analysis Collector Plug-in >>>> 4) Checkstyle Plug-in >>>> 5) PMD Plug-in >>>> 6) FindBugs >>>> 7) DRY >>>> >>>> My issue is no results are showing up when I do a build. I have enabled >>>> the project to get these results. What gives? >>>> >>>> thanks, >>>> Rob >>> >> >
