Hi, It seems that there is no Sonar analysis of Jenkins in the Jenkins-CI infrastructure. Perhaps, it could be added there one day: https://jenkins.ci.cloudbees.com/
But, for curious people about Findbugs and others violations in Jenkins code, you can look at: http://nemo.sonarqube.org/dashboard/index/org.jenkins-ci.main:jenkins-core (This seems to be regularly updated, but be warned that the rules configuration are certainly not customized for the Jenkins project) @Jesse There is a link "Sonar as a service for your project with CloudBees" on the left of that Sonar page, and we may try it (just kidding ;-) bye, Emeric Le lundi 24 février 2014 14:56:37 UTC+1, Jesse Glick a écrit : > > On Sun, Feb 23, 2014 at 4:48 PM, Oleg Nenashev > <[email protected]<javascript:>> > wrote: > > Seems that Coverity has discovered new issues (compared to FindBugs) > > I looked through a few dozen examples and saw little it was catching > that FindBugs would not also pick up. Since we have made no serious > effort to address the numerous issues that FB is already warning us > of, I see little point in adding a proprietary tool to the mix, with > the implied overhead of keeping it licensed and running. > > FWIW I keep a FindBugs plugin running in my IDE so that its warnings > show up automatically in the editor. This helps me usually keep any > new code I write clean of common FB warnings, and sometimes I will fix > up important-looking violations in code related to things I am > patching. But you hardly need spend much time looking for bugs to fix > in Jenkins; I do not know of anyone consistently triaging incoming > JIRA reports, so picking over minor static analysis warnings seems a > low priority. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
