|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I am assuming this is a checkstyle bug, but it could be whatever portion of Jenkins builds the Project view UI for a project. Regardless or whether or not a project is built by a master or slave server, PMD and Findbugs generate their XML files and place them in the project's workspace directory. This directory is "${jenkins home directory}/jobs/${project name}/workspace".
NOTE: As stated in the bug report, ${jenkins home directory} is a mounted directory available on both master and slave servers. Both servers are using the same physical directory.
The workspace link on the project UI displays a path of "${tomcat server}:8080/jenkins/view/${jenkins view name}/job/${jenkins project name}/ws" when you hover the mouse over it. I don't know where this address maps to physically with respect to the ${jenkins home directory} variable.
But, when a build is done on the master server, this link works and somehow points to the files that were stored in "${jenkins home directory}/jobs/${project name}/workspace". When a build is done on a slave server, this link points to an empty directory somewhere. Thus checkstyle cannot find the XML files to update the warnings graphs (and gives a parsing error).