Hi,
I was wondering if there are any suggestions about how I could perform a
local check of "new warnings based on reference build".
The use case is where there are a number of warnings in the build that are
tolerated because they are considered "legacy warnings", but we don't want
to allow an
I've opened "PMD Plugin reporting existing warnings as new"
https://issues.jenkins-ci.org/browse/JENKINS-14509
- David
On Thursday, July 19, 2012 4:58:45 PM UTC+3, Ulli Hafner wrote:
>
> Seems that the context hash code is not computed. Are the filenames
> correct? Is this a maven or freestyle
Which file plug-in file created file do you need exactly?
jenkins\jobs\job-name\builds\2012-07-19_13-38-36\pmd-warnings.xml?
Would it be enough for me to find the equivalent entries in the
pmd.xml/pmd-warnings.xml files?
For example:
pmd.xml:
http://pmd.sourceforge.net/rules/java/logging-java.
Yes, definitely the same PMD version. Before the PMD upgrade there were no
PMD warnings.
The amount of warnings that are detected as new or existing seems almost
random. It usually shows all warnings as new, but it sometimes detects some
10's or 100's as existing.
- David
On Thursday, July 19
Hi,
I'm using the PMD plugin to detect and monitor PMD warnings that are found
in my builds. I recently upgraded to PMD 5.0 and added a number of new PMD
rules to my report.
My problem is that the PMD plugin seems to be almost completely incapable
of differentiating between new and previously
Could you add --debug to the gradle execution and post the results here?
- David
On Wednesday, June 6, 2012 9:55:03 PM UTC+3, Ken Krebs wrote:
>
> I'm having difficulty getting my freestyle Jenkins job to execute my
> Gradle build. After it checks out the code from SVN it simply
> finishes : SU
