Managing builds with huge number of inspection problems?

I am working on a project with a very large number of legacy inspection problems that cannot be fixed in bulk. The volume of problems means that an inspection build result report is to large to provide much value.

Currently I am using a hand-rolled intergration of checkstyle with cruisecontrol, which as part of each build runs checkstyle against only those files changed since the last build. This reduces the volume of messages to something closer to managable. I'm wondering if anyone has thoughts on how to address this issue using TeamCity.

I've opened a Jira issue with my suggestions:
http://www.jetbrains.net/jira/browse/TW-785 (provide a mechanism to find problems relative to previous builds)

7 comments
Comment actions Permalink

Hello Johannes,

It is planned for Release 1.5.
It is really not so easy to detect which problem is new and which problem
just 'move to the new line'.

Thank you.

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

I am working on a project with a very large number of legacy
inspection problems that cannot be fixed in bulk. The volume of
problems means that an inspection build result report is to large to
provide much value.

Currently I am using a hand-rolled intergration of checkstyle with
cruisecontrol, which as part of each build runs checkstyle against
only those files changed since the last build. This reduces the volume
of messages to something closer to managable. I'm wondering if anyone
has thoughts on how to address this issue using TeamCity.

I've opened a Jira issue with my suggestions:
http://www.jetbrains.net/jira/browse/TW-785 (provide a mechanism to
find problems relative to previous builds)



0
Comment actions Permalink

There would be great value even in a fairly simplistic algorithm for reducing the volume, for example filtering for problems only in files changed since the last build.

0
Comment actions Permalink

Johannes,

This isn't complicated indeed. But it is not good in many situations. E.g.
you deleted code which invoked your method. The file with method wasn't changed.
But the method become unused ...

I suggest a special filter on the page with inspection results to filter
all unmodified files.

What do you think?

Thanks.

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

There would be great value even in a fairly simplistic algorithm for
reducing the volume, for example filtering for problems only in files
changed since the last build.



0
Comment actions Permalink

That would be a great improvement. Perhaps also a filter for files "modified by me", possible as a link from the "my changes" page.

Looking forward to seeing the "ultimate" solution in 1.5 :)

0
Comment actions Permalink

Johannes Graham wrote:

That would be a great improvement. Perhaps also a filter for files "modified by me", possible as a link from the "my changes" page.
Looking forward to seeing the "ultimate" solution in 1.5 :)


Current EAP (build 1631) contains functionality to filter "new"
inspection results (enabled by default). It will be great to hear your
feedback on it.

--
Alexey Gopachenko
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

Looks good!

One glitch so far: if you unselect, then reselect the box, the page does not update as expected. ( http://www.jetbrains.net/jira/browse/TW-878 )

Out of curiosity, is this simply reporting only those errors that occurred in modified files, or is it truly showing all errors that did not exist in the last build?

0
Comment actions Permalink

Yes, it really counts and shows all the errors that did not exist in the
last build.

--
Alexey Gopachenko
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0

Please sign in to leave a comment.