Re: Findbugs report with excluded packages
It's hard to see if your filters are correct if you don't post your filter. But anyway, if the findbugs.xml does not contain the warnings and findbugsXml.xml does contain the warnings then this seem to be a bug in the maven findbugs plug-in. Which version are you using? Ulli On 04/16/2012 11:42 AM, jhoomshar...@netscape.net wrote: I looked into it and did not found any issue with reports generated by mvn findbugs:findbugs command the html report generated looks good, but the xml reports findbugsXml.xml still shows excluded class and packages under Jenkins Findbugs report, this is strange and I have no idea why and how this is happening, do I need to configure anything more in findbugs plug-in to exclude the packages, I don't think I have to any more configuration in findbugs plugin the exclude list should take care of exclude packages, Or do I need to put exclude list under each modules rather than using it only in parent pom? Any help in this regard is highly appreciated. -Original Message- From: Ullrich Hafner ullrich.haf...@gmail.com mailto:ullrich.haf...@gmail.com To: jenkinsci-users jenkinsci-users@googlegroups.com mailto:jenkinsci-users@googlegroups.com Sent: Thu, Sep 29, 2011 6:48 pm Subject: Re: Findbugs report with excluded packages The FindBugs Jenkins plug-in does not read the exclude filters specified in your pom it just renders the results of the maven plug-in. I.e., this must be a problem in your filter configuration. Ulli On 09/29/2011 02:44 PM, Christoph Kutzinski wrote: Is it working if you call mvn install findbugs:findbugs manually, i.e. from a shell? If not, we need to see your exclude and include files. Original-Nachricht Datum: Thu, 29 Sep 2011 08:22:26 -0400 (EDT) Von: jhoomshar...@netscape.net mailto:jhoomshar...@netscape.net An: jenkinsci-users@googlegroups.com mailto:jenkinsci-users@googlegroups.com Betreff: Findbugs report with excluded packages I am using Jenkins findbugs plugin v4.29, now I configured my pom to exclude few packages, but when I run my project which contains configuration mvn install findbugs:findbugs I am still seeing that findbugs is generating report for excluded packages, I have no idea if this is an issue with findbugs maven plugin or findbugs Jenkins plugin, my pom with finbugs configuration looks like this plugin groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version2.3.1/version configuration findbugsXmlOutputtrue/findbugsXmlOutput findbugsXmlWithMessagestrue/findbugsXmlWithMessages xmlOutputtrue/xmlOutput excludeFilterFilefindbugs-exclude.xml/excludeFilterFile includeFilterFilefindbugs-include.xml/includeFilterFile /configuration /plugin Any help in this regard will be highly appreciated. Thanks, Jhoom
Re: clean up maven repo in Jenkins slave
Hi Domi, this is a great help. I have more questions. where can I check/change the home directory of my user jenkins running with? Is that a good idea if i put maven repos in a share drive and mount it on both maven and jenkins slave servers so that only one location should be cleared up once too many dependencies are there and maven does not need to copy files to jenkins slave when build job running? Thanks, Jason On Apr 14, 3:02 am, domi d...@fortysix.ch wrote: It's not jenkins who copies the dependencies to this location, its maven. There are multiple reasons which could cause this: - you have configured /opt to be the home directory of your user you running jenkins with. - this location is configured in your settings.xml If you delete all these, maven will just download them the next time again (and slow down the build). If you have multiple maven jobs running at the same time, you should also not delete the directory/repository while a build is running, this would just remove the needed libraries and the build will fail. I recommend you use the 'Config File Provide Plugin' [1] - this will allow you to configure your settings.xml at a central place and select one within your job configuration from a drop down menu. regards Domi [1]https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin On 13.04.2012, at 20:43, JasonX wrote: I saw maven repo is copied to /opt/.m2 directory on Jenkins slave from maven server and it fills up Jenkins slave disk. I wanna clean it up. How can I do it? can I remove all of the repos from Jenkins slave after each build? is that necessary to keep all dependencies on Jenkins slave but they are already existing in maven server.
Re: Disable auto-update / Switching to LTS
On Mon, Apr 16, 2012 at 10:35 AM, Neil Bird n...@fnxweb.com wrote: Around about 16/04/12 10:08, Markus typed ... How can I disable that Jenkins automatically updates itself? We are running on CentOS and using the RedHat Linux RPM packages for Jenkins. Our system admin has ensured me that the OS does not upgrade Jenkins. Then I would have to suggest that he's wrong; do you have yum-autoupdate installed? 'Cos that would do it. If so, uninstall it, or edit /etc/sysconfig/yum-autoupdate I don't know if you can selectively not update just jenkins. Otherwise, I don't know of any [default] mechanism where jenkins *would* update. Even if it isn't doing auto-updates, jenkins might update along with the rest of the system whenever a 'yum update' is done. To stop it, edit /etc/yum.repos.d/jenkins.repo and add a line that says enabled=0. Then it will only update if you change it to enabled=1 or override on the yum command line with --enablerepo=jenkins. -- Les Mikesell lesmikes...@gmail.com
Re: WARNING: Failed to advertise the service to DNS multi-cast
Hello Sami, Thank you very much for the update and follow-up. So this issue is not happening for me anymore but I am not sure why. I have tried to things: The first one was to start Jenkins with the following option -Dhudson.DNSMultiCast.disabled=true but this did not seem to have any effects because I would see the issue when I restarted Jenkins Then I moved on to configured mail did that restarted Jenkins and I no longer saw the issue. I have open an issue per your request. My Jenkins address is my ip address On Friday, April 13, 2012 2:56:27 PM UTC-7, sti wrote: I'm afraid that might be caused by the recent fix I made to Jenkins mDNS advertisement. It almost seems like Jenkins is unable to parse its own address. What do you have set as Jenkins' own address in Manage Jenkins / Configure system? Would you mind reporting the bug into issues.jenkins-ci.org? Frankly I do not know if the exception causes something else to be skipped in the startup. -- Sami SamL lopez@gmail.com kirjoitti 13.4.2012 kello 20.02: Hello Folks. I just installed Jenkins ver. 1.459 on a CentOS 6 machine and I am getting the following WARNING during start up. Does anyone know what this mean and is it something I should be concern about? Does anyone know what this w WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:617) at java.net.URL.init(URL.java:480) at java.net.URL.init(URL.java:429) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.init(URL.java:522) ... 7 more Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running
Re: WARNING: Failed to advertise the service to DNS multi-cast
I don't think I did anything different but it stopped happening for me after upgrading to 1.460 (Windows). fyi --- On Mon, 4/16/12, SamL lopez@gmail.com wrote: From: SamL lopez@gmail.com Subject: Re: WARNING: Failed to advertise the service to DNS multi-cast To: jenkinsci-users@googlegroups.com Date: Monday, April 16, 2012, 2:11 PM Hello Sami, Thank you very much for the update and follow-up. So this issue is not happening for me anymore but I am not sure why. I have tried to things: The first one was to start Jenkins with the following option -Dhudson.DNSMultiCast.disabled=true but this did not seem to have any effects because I would see the issue when I restarted Jenkins Then I moved on to configured mail did that restarted Jenkins and I no longer saw the issue. I have open an issue per your request. My Jenkins address is my ip address On Friday, April 13, 2012 2:56:27 PM UTC-7, sti wrote:I'm afraid that might be caused by the recent fix I made to Jenkins mDNS advertisement. It almost seems like Jenkins is unable to parse its own address. What do you have set as Jenkins' own address in Manage Jenkins / Configure system? Would you mind reporting the bug into issues.jenkins-ci.org?Frankly I do not know if the exception causes something else to be skipped in the startup.-- SamiSamL lopez@gmail.com kirjoitti 13.4.2012 kello 20.02: Hello Folks. I just installed Jenkins ver. 1.459 on a CentOS 6 machine and I am getting the following WARNING during start up. Does anyone know what this mean and is it something I should be concern about? Does anyone know what this w WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java: 617) at java.net.URL.init(URL.java: 480) at java.net.URL.init(URL.java: 429) at hudson.DNSMultiCast.init( DNSMultiCast.java:45) at jenkins.model.Jenkins.init( Jenkins.java:787) at hudson.model.Hudson.init( Hudson.java:81) at hudson.model.Hudson.init( Hudson.java:77) at hudson.WebAppMain$2.run( WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.init(URL.java: 522) ... 7 more Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running
RE: Jenkins SLOCCount plugin - unable to see job configuration option after plugin install
Nothing in the log file and we are only seeing this on multi-config jobs. When we create a job from scratch the options show up fine. Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Neil Bird Sent: Monday, April 16, 2012 8:27 AM To: jenkinsci-users@googlegroups.com Subject: Re: Jenkins SLOCCount plugin - unable to see job configuration option after plugin install Around about 13/04/12 22:15, Buser, Stephanie typed ... We recently installed the SLOCCount plugin but are unable to see the “Publish SLOCCount analysis results” on the job configuration page (i.e. under the post-build actions). Is there anything in the Jenkins log file? Maybe it's looking for sloccount, not finding it for some reason, and disabling itself? It always “just worked” for me. -- [neil@fnx ~]# rm -f .signature [neil@fnx ~]# ls -l .signature ls: .signature: No such file or directory [neil@fnx ~]# exit Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Buser, Stephanie Sent: Friday, April 13, 2012 2:15 PM To: jenkinsci-users@googlegroups.com Subject: Jenkins SLOCCount plugin - unable to see job configuration option after plugin install Hi, We recently installed the SLOCCount plugin but are unable to see the “Publish SLOCCount analysis results” on the job configuration page (i.e. under the post-build actions). We’ve tried completely uninstalling and reinstalling the plugin with no luck. Has anyone come across this issue and if so is there a solution for it? Is there anything we need to be configuring outside of the instructions on the install page? Perhaps another installed plugin is overriding the configuration for the SLOCcount plugin? https://wiki.jenkins-ci.org/display/JENKINS/SLOCCount+Plugin Thanks!
fonts in junit trend graphs are unreadable
I've just set up Jenkins to run PHPUnit tests. Everything is working fine except that the junit trend graphs are very difficult to read. The font is all wrong. https://img.skitch.com/20120416-deuen41cigddrgt7nfyhmyi3f4.png I'm unsure how to further research this issue. (Searches for 'trend report font' similar haven't produced anything useful.) Can anyone offer any pointers? thanks, alex Centos 5.6 $ java -version java version 1.6.0_20 OpenJDK Runtime Environment (IcedTea6 1.9.8) (rhel-1.22.1.9.8.el5_6- x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) $ rpm -qa | grep jenkins jenkins-1.460-1.1
ERR_CONTENT_DECODING_FAILED when try to access job configuration pages
Hi, I'm getting Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. in Chrome when I try to access job configuration pages. Firefox gives a more generic error but also cannot access it. This is on Jenkins 1.459 running on Ubuntu 11.10. Nothing is showing up in the Jenkins Log. This happens on all my projects even when I create a new job (can't even set any of the settings but it still creates the empty job). Does anyone have ideas what could cause this? I am about to try restarting after some builds finish. And it works after restarting but I still want to send this out in case anyone gets a similar error. It may be related to just installing 1.459 last Friday, not sure exactly which version I was on before that but it was probably around a month old. Thanks, Jason
Re: ERR_CONTENT_DECODING_FAILED when try to access job configuration pages
Hi Jason, I had this same problem with 1.458 on CentOS (due to the gzip page compression introduced then) see https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-users/cobertura/jenkinsci-users/OJxWOXpSsMs/ReNTRVSFkFAJ I upgraded this morning to 1.460 and the problem disappeared: you may also try the update. regards didier Le mardi 17 avril 2012 06:45:12 UTC+2, Jason Axelson a écrit : Hi, I'm getting Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. in Chrome when I try to access job configuration pages. Firefox gives a more generic error but also cannot access it. This is on Jenkins 1.459 running on Ubuntu 11.10. Nothing is showing up in the Jenkins Log. This happens on all my projects even when I create a new job (can't even set any of the settings but it still creates the empty job). Does anyone have ideas what could cause this? I am about to try restarting after some builds finish. And it works after restarting but I still want to send this out in case anyone gets a similar error. It may be related to just installing 1.459 last Friday, not sure exactly which version I was on before that but it was probably around a month old. Thanks, Jason
