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 e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
