[JIRA] (JENKINS-12955) Stylecop file report is blank

[eric.tho...@seca.com (JIRA)]

Eric Thomas edited a comment on JENKINS-12955 Stylecop file report is blank The error seems to be related to our recent update of both, hudson (1.395) to jenkins (V1.480.3), and Violations 0.7.7 to 0.7.11. Prior to that, everything worked fine. Now, even reports which have been created before the update won't show up in the detailed file page. Interestingly, Violations seems to create distinct report files for FxCop and StyleCop now. Moreover, the files created for StyleCop do not contain the lines copied from the original source files while the xml created for FxCop does contain this information. While the xml which has been created for builds before our update contains this line information, it is not crated anymore. Here is an example of a newly created report file called [PROJECT]\builds[DATETIME]\violations\file\HudsonDATA\jobs[PROJECT]\workspace[PATH_WITHIN_PROJECT][ORIGINAL_FILENAME].xml (Note that FxCop reports for the same file are stored under [PROJECT]\builds[DATETIME]\violations\file\PATH_WITHIN_PROJECT][ORIGINAL_FILENAME].xml, so the workspace notion is missing here): <?xml version="1.0" encoding="UTF-8"?> <file name="HudsonDATA/jobs/PROJECT/workspace/Development/Sources/Properties/AssemblyInfo.cs" last-modified="0" > <violation line="1" source="DocumentationRules" severity="Medium" type="stylecop" message="The file has no header, the header Xml is invalid, or the header is not located at the top of the file. (SA1633)" severity-level="2" popup-message="The file has no header, the header Xml is invalid, or the header is not located at the top of the file. (SA1633)" /> <violation line="9" source="LayoutRules" severity="Medium" type="stylecop" message="A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1512)" severity-level="2" popup-message="A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1512)" /> <violation line="23" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="24" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="25" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="26" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="27" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="28" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="30" source="LayoutRules" severity="Medium" type="stylecop" message="A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1512)" severity-level="2" popup-message="A single-line comment must not be followed by a blank line. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1512)" /> <violation line="30" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="32" source="LayoutRules" severity="Medium" type="stylecop" message="The code must not contain multiple blank lines in a row. (SA1507)" severity-level="2" popup-message="The code must not contain multiple blank lines in a row. (SA1507)" /> <violation line="34" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="35" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="37" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="38" source="SpacingRules" severity="Medium" type="stylecop" message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" severity-level="2" popup-message="The comment must start with a single space. To ignore this error when commenting out a line of code, begin the comment with '////' rather than '//'. (SA1005)" /> <violation line="42" source="LayoutRules" severity="Medium" type="stylecop" message="The code must not contain multiple blank lines in a row. (SA1507)" severity-level="2" popup-message="The code must not contain multiple blank lines in a row. (SA1507)" /> <type type='stylecop' number='16' suppressed='0'/> </file>

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.