Hi all,
After all recent discussions about performance issues and donations,
I'm thinking Code Quality Analysis should be a topic in CBI. There
are some very good tools, such a Sonar, that are easy to use and
which provide great insights on the code quality, that spots some
deffects much faster than a test, and that sometimes include some
rules that shows which pieces of code can cost a lot of
performances.
Code Quality Analysis is a requirement for continuous improvement.
I've asked for a Sonar instance a while ago (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=360935 ) and still
nothing happened. It looks like my voice is not strong enough to
make it a priority. What would you think of making code quality
analysis part of CBI ? I don't think it's a huge effort since Sonar
provides all necessary integration (Maven, Hudson) to make it as
easy as ticking a checkbox in Jenkins/Hudson and adding a couple of
properties in your pom.
Also, having Tycho + Sonar makes it quite easy to set up Jacoco
reports and get coverage for almost free.
This is IMO a very important topic for the future of Eclipse. There
are now some very good tools to get meaningful and useful quality
metrics, and we must admit that except JUnit reports, there is no
such metric for most Eclipse projects. Having this tool will clearly
make Eclipse better.
If you can make code analysis part of CBI, that will probably
increase the priority of issue 360935. When such a Sonar server gets
available at Eclipse, I'll be glad to help in setting up reports for
Platform build if you need it.
Cheers,
|