Re: no code analysis showing up with my builds

Well now, Dirk and Ulli, I have some analysis results in Jenkins, as it turns out. It just doesn't fall under my project murmur-events, it is a level below, which is weird. Here is my project page: http://callistosheart:/job/murmur-events/ Here is my project page for the latest build: ht

Re: no code analysis showing up with my builds

http://callistosheart:/job/murmur-events/lastFailedBuild/console Rob -Original Message- From: Dirk Weigenand Sent: Thursday, October 04, 2012 5:14 PM To: jenkinsci-users@googlegroups.com Subject: Re: no code analysis showing up with my builds Hi, i slightly changed your pom.xml.

Re: no code analysis showing up with my builds

I just realized I do not really care about checkstyle, just PMD and findbugs. I am hoping the duplicate code plugin works in Jenkins. So, I removed checkstyle from my pom.xml and everything is working from the CLI, when I run it either individually or as you suggested: 'mvn clean' good! 'mv

Re: no code analysis showing up with my builds

Hi Dirk, Thanks for your patience. It still is not working, although progress has been made. I have pushed my entire project to https://github.com/reefedjib/murmur-events, if you would like to help me take a look. I am down to one problem, running it at the CLI. Get that working then tu

Re: no code analysis showing up with my builds

Hi, i slightly changed your pom.xml. A small java source in the default package under src/main/java shows up fine in all reports. regards Dirk PS: Using the following command line 'mvn clean package pmd:pmd checkstyle:checkstyle findbugs:findbugs' that is. On 04.10.2012 22:11, Rob With

Re: Switching from bleeding edge to LTS?

OK, then I think that if I: 1) switch my latest&greatest plugin update to point to the stables now 2) stop upgrading core until LTS reaches that version or higher I should be in the clear Thank you for the response. 2012/10/4 teilo : > Downgrading to an earlier lts may not work if the mainline

Re: no code analysis showing up with my builds

I am attaching the 3 config files for analysis where I changed the file references to the project root. I still have the error below: Caused by: java.io.FileNotFoundException: C:\rob\comp\workspace\murmur-events\target\checkstyle-suppressions.xml Rob -Original Message- From: Rob W

Switching from bleeding edge to LTS?

Downgrading to an earlier lts may not work if the mainline version has changed any configuration (although it might work as well). Since I stopped taking the mainline and moved to lts I've found far far fewer suprises. Downside is you don't see the new experimental stuff so can't provide feedb

Re: no code analysis showing up with my builds

I fixed the JUnit issue. I thought this section of the POM specified the etc directory: install etc true ... "I think the setup used in the analysis-plugin family does not play well with your use case (one project with analysis configuration within the project)." h

Re: no code analysis showing up with my builds

Hi, prefix your configuration files with 'etc/'. I think the setup used in the analysis-plugin family does not play well with your use case (one project with analysis configuration within the project). regards Dirk On 04.10.2012 19:56, Rob Withers wrote: > I am now getting this error:

Re: no code analysis showing up with my builds

Interesting...I now have the following files in my target directory, but nothing for pmd. Same error as the last email findbugsCheck.xml findbugsTemp.xml (0 kb) checkstyle-checker.xml checkstyle-header.txt checkstyle-result.xml (0 kb) I deleted everything in that target folder to regenera

Re: no code analysis showing up with my builds

I am now getting this error: Caused by: org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find resource 'checkstyle-configuration.xml'. I am attaching my pom.xml and the xml config files for the analysis tools are in the folder 'etc'. I think that is everything to desc

Re: Warnings plugin: Slow Performance with custom regexp

You can see which changes are in a release in github: https://github.com/jenkinsci/warnings-plugin/commits/master The issue you are referring to is part of release warning@4.15 and analysis-core@1.45. Ulli Am 04.10.2012 um 16:01 schrieb Jon Payne : > Hi all, > > We've experience a massive slo

Switching from bleeding edge to LTS?

Hi. We currently run latest and greatest of Jenkins (and plugins), but are experiencing unstability from time to time, so I'm thinking of switching to LTS. Can I just downgrade my RPM to the LTS one and everything should still run smoothly? What about all the plugins we've currently installed (whi

Perforce changes since last successful build

Does anybody have a recipe for getting the Perforce changelists since the last successful/stable build. I'd like to include that information in notification emails and perhaps also use it to drive the recipient lists. It's clear that the plugin is able to get the changelists since the last bui

Re: Perforce plugin and P4TICKET variable

P4TICKET is saved between syncs... so it should always be available. If it's not, then it means there's a bug in the plugin. On Wednesday, 3 October 2012 10:52:56 UTC-6, Richard J wrote: > > Our Perforce server is set at security level 3 and the build scripts need > to use the P4TICKET variable

Warnings plugin: Slow Performance with custom regexp

Hi all, We've experience a massive slow down in parsing of warnings with a custom regexp. It appears that the issue was fixed but that this patch never made it into a release as far as I can tell: Warnings Plugin: Slow Performance on customized parsing rules with Regular Expression

Re: Email-ext plugin does not work with testng results

Dear All, I've found a workaround: because the Testng's ant task also generates the junit compatible reports we can use that for putting the failed tests to the emails. Just the Junit report publisher to the Jenkins project, and set the "Test report XMLs" to find the junit formatter xmls, like:

Email-ext plugin does not work with testng results

Dear Developers, We have the same problem that already described in an issue, that the email-ext plugin does not include the failed tests in the emails when used with testng. The bug is filed here: [https://issues.jenkins-ci.org/browse/JENKINS-10340], but unfortunately that is set to "won't fi

Re: no code analysis showing up with my builds

Hi, just copy over the relevant parts of the pom.xml ... etc true org.apache.maven.plugins maven-resources-plugin 2.4.3 ${source.encoding} and don'

Re: no code analysis showing up with my builds

Hi Dirk, I took a little time and looked at this. It doesn't look like a good example of the use of the POM to reference these tools. Is there a better example that has a POM setup to use these tools? I poked around a bit but I did not find anything. Rob -Original Message- From

Re: no code analysis showing up with my builds

Ok, cool. I have to run for the day, but I will jump into it this afternoon Thanks! Rob -Original Message- From: Dirk Weigenand Sent: Thursday, October 04, 2012 7:42 AM To: jenkinsci-users@googlegroups.com Subject: Re: no code analysis showing up with my builds Hi, have a look

Re: no code analysis showing up with my builds

Hi, have a look at how the analysis-plugin family is structured. All plugins depend on this plugin: https://github.com/jenkinsci/analysis-config-plugin which holds the configuration for the various maven static source code analysis plugins used throughout the build. regards Dirk On 04.10.2012

Re: no code analysis showing up with my builds

Ok, I removed the zips and harvested the plugins from your POM. I removed the dependencies sections. Issue 1: when I go to the cli and run 1) mvn findbugs:findbugs 2) mvn checkstyle:checkstyle 3) mvn pmd:pmd in all cases it fails due to a missing configuration xml file specific for that tool.

Re: setting up git SCM...

Hi, On 03.10.2012 16:21, Rob Withers wrote: > I stopped using git and went back to what was working before, which was > setting up a maven2 project. Now I develop in eclipse and I can launch > a build manually, whenever I want to build the jar and run the tests. > To get it working, I set the gl

Re: no code analysis showing up with my builds

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)

Re: no code analysis showing up with my builds

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 the

Build whenever a SNAPSHOT dependency is built - Gradle/Jenkins integration?

This is a cross post from: http://forums.gradle.org/gradle/topics/build_whenever_a_snapshot_dependency_is_built_gradle_jenkins_integration?rfm=1 When building a maven project on Jenkins its possible to specify the build trigger: Build whenever a SNAPSHOT dependency is built This works out of th