|
||||||||
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 |
- [JIRA] (JENKINS-14509) PMD Plugin reporting... abune...@gmail.com (JIRA)
- [JIRA] (JENKINS-14509) PMD Plugin repo... abune...@gmail.com (JIRA)
- [JIRA] (JENKINS-14509) PMD Plugin repo... abune...@gmail.com (JIRA)
- [JIRA] (JENKINS-14509) PMD Plugin repo... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14509) PMD Plugin repo... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14509) PMD Plugin repo... fush820...@163.com (JIRA)
The contextHashCode values do seem to be almost contiguous – they all seem to be between 7000-9000. Not as I'd expect hash values to be.
Yes, the fileName element in the pmd-warnings.xml file holds the correct filename for the most recent job run. Note that the job may run in different locations depending on the Jenkins slave that was used.
How is the filename used? They are the full, not relative path to the file in the job workspace.