Violations plug-in not showing errors or source

[Daniel Becroft]

Hi,

Since upgrading to a recent release (currently on 1.448, but it was happening before that), the Violations plugin is no longer generating the detail page(s) for each source code file. The code reports are successfully being parsed, and the graphs/file lists are fine. But, clicking on the filename just shows a blank page with the violations icon - no source, no error list, nothing.

Are there any error files that I should look at for exception information? I can't see anything being updated with recent datetime information.

---
Daniel Becroft

[Daniel Becroft]

Does anyone have any clues for me? Or somewhere else I should raise this issue?
---
Daniel Becroft

On Fri, Jan 27, 2012 at 10:07 AM, Daniel Becroft <[hidden email]> wrote:

Hi,

Since upgrading to a recent release (currently on 1.448, but it was happening before that), the Violations plugin is no longer generating the detail page(s) for each source code file. The code reports are successfully being parsed, and the graphs/file lists are fine. But, clicking on the filename just shows a blank page with the violations icon - no source, no error list, nothing.

Are there any error files that I should look at for exception information? I can't see anything being updated with recent datetime information.

---
Daniel Becroft

[gregarmer]

Daniel Becroft wrote

Does anyone have any clues for me? Or somewhere else I should raise this
issue?
---
Daniel Becroft

Hi Daniel,

I recently ran into this problem while using the pylint and pep8 checks in the violations plugin, the actual issue in my case was that the paths to these files are relative and the detail view couldn't find them. I changed my build steps to run the pylint and pep8 checks from the root of the workspace and the links all started working again.

Perhaps something similar might help you ?

Good luck.

--
Greg Armer

[Alex-3]

On Jan 27, 3:07 am, Daniel Becroft <[hidden email]> wrote:

> Hi,
>
> Since upgrading to a recent release (currently on 1.448, but it was
> happening before that), the Violations plugin is no longer generating the
> detail page(s) for each source code file. The code reports are successfully
> being parsed, and the graphs/file lists are fine. But, clicking on the
> filename just shows a blank page with the violations icon - no source, no
> error list, nothing.
>
> Are there any error files that I should look at for exception information?
> I can't see anything being updated with recent datetime information.

Did you find a solution to this?  I am seeing the same issue - graph
and general report generated fine, but viewing individual reports in
Jenkins shows an empty page (the report XML files contain full info
though).

[Daniel Becroft]

 Thu, Oct 25, 2012 at 8:29 PM, Alex <[hidden email]> wrote:

On Jan 27, 3:07 am, Daniel Becroft <[hidden email]> wrote:
> Hi,
>
> Since upgrading to a recent release (currently on 1.448, but it was
> happening before that), the Violations plugin is no longer generating the
> detail page(s) for each source code file. The code reports are successfully
> being parsed, and the graphs/file lists are fine. But, clicking on the
> filename just shows a blank page with the violations icon - no source, no
> error list, nothing.
>
> Are there any error files that I should look at for exception information?
> I can't see anything being updated with recent datetime information.

Did you find a solution to this?  I am seeing the same issue - graph
and general report generated fine, but viewing individual reports in
Jenkins shows an empty page (the report XML files contain full info
though).

Nope, never got a reply or a solution for it. 

Regards,

Daniel B.

[Alex-3]

On 26 October 2012 04:39, Daniel Becroft <[hidden email]> wrote:
>> Did you find a solution to this?  I am seeing the same issue - graph
>> and general report generated fine, but viewing individual reports in
>> Jenkins shows an empty page (the report XML files contain full info
>> though).
>
>
> Nope, never got a reply or a solution for it.

Shame.  I had a go at fixing this, and came up with something that
works...for me.  It's not clear to me whether what I've done is
actually a fix or a hacky mess (so likely the latter), but might be
worth a try if you're still interested - you can get the source at
https://github.com/alxndrsn/jenkins-violations-plugin, build with
`maven clean install` and install target/violations.hpi from the
plugin manager's Advanced tab.