• Type: Bug
• Resolution: Not A Defect
• Priority: Minor
• Component/s: checkstyle-plugin
• Labels:

  None
• Environment:

  Jenkins ver. 1.615
  checkstyle-plugin 3.42
  checkstyle 6.1.1

[JENKINS-28746] Plugin only publish first result file

Collapse comment: Ulli Hafner added a comment - 2015-06-04 11:56

Ulli Hafner added a comment - 2015-06-04 11:56

Can you please elaborate?

Is there a warning in checkstyle-result.xml of Warehouse Parent POM?
What do you mean with suddenly? Did you change anything in your setup?

Are there other result files that are not parsed?

Expand comment: Ulli Hafner added a comment - 2015-06-04 11:56

Ulli Hafner added a comment - 2015-06-04 11:56 Can you please elaborate? Is there a warning in checkstyle-result.xml of Warehouse Parent POM? What do you mean with suddenly ? Did you change anything in your setup? Are there other result files that are not parsed?

Collapse comment: C. S. added a comment - 2015-06-04 13:18

C. S. added a comment - 2015-06-04 13:18

Thanks for your fast reponse.
To be honest, I don't know what I can tell you to give more information. I am really confused.

In my opinion checkstyle-result.xml contains all scanned files and the errors/warnings of the check.
In my case the file checkstyle-result.xml contains only all scanned files and the console tells me there a X errors.

Finally I found my mistake ... I did run first checkstyle:checkstyle on the tests resources and run checkstyle:check on main using in both cases the same outputFile.
I was expecting that checkstyle:check just breaks and don't dump any file.

That explains the checkstyle-result.xml on Jenkins containing only scanned files from main.

The real background behind this issue was that Jenkins doesn't load any checkstyle-result.xml any more. I think it was overwritten by the two executions.

Expand comment: C. S. added a comment - 2015-06-04 13:18

C. S. added a comment - 2015-06-04 13:18 Thanks for your fast reponse. To be honest, I don't know what I can tell you to give more information. I am really confused. In my opinion checkstyle-result.xml contains all scanned files and the errors/warnings of the check. In my case the file checkstyle-result.xml contains only all scanned files and the console tells me there a X errors. Finally I found my mistake ... I did run first checkstyle:checkstyle on the tests resources and run checkstyle:check on main using in both cases the same outputFile. I was expecting that checkstyle:check just breaks and don't dump any file. That explains the checkstyle-result.xml on Jenkins containing only scanned files from main. The real background behind this issue was that Jenkins doesn't load any checkstyle-result.xml any more. I think it was overwritten by the two executions.