On 08/24/2012 11:20 AM, matthew.web...@diamond.ac.uk wrote: > The Jenkins Warnings plugin > (https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) allows us to > select (via a regex) which files we want to analyse. However, I could not see > any way to exclude certain warnings we are not interested in. Can this be > done? > > Use case: We have a large, old code base which has 1400 warnings (cough). A > fair number of those are deprecation warnings. I'm started insisting that > whenever a developer commits a change to a class, they MUST not introduce any > new warnings, and they SHOULD fix up any existing warnings (except > Deprecation warnings). > > It would help if I could (temporarily) exclude deprecation warnings from the > analysis, since they are lower priority. > > Matthew > > This is not possible (in the plug-in) yet.
In order to work in a general way we need to define for each parser a set of warning type/rule identifiers (like this is done in FindBugs or Checkstyle). And on the UI part we need the possibility to define the rules that will be used (or will not). As a workaround you can either filter/grep the output to a file that is scanned by the parser. Or you can extend the current parser (or write a new one) that does the filtering in code. (You can use the UI to define the new parser) Ulli
