On Tuesday, May 1, 2012 4:04:25 AM UTC+1, djcbecroft wrote: > > On Tue, May 1, 2012 at 12:17 PM, Daniel Becroft <djcbecr...@gmail.com>wrote: > >> On Mon, Apr 30, 2012 at 5:28 PM, Ullrich Hafner <ullrich.haf...@gmail.com >> > wrote: >> >>> On 04/29/2012 10:46 PM, Daniel Becroft wrote: >>> >>> On Wed, Mar 21, 2012 at 6:34 PM, timos <timo.j.sillan...@gmail.com>wrote: >>> >>>> The same problem here. At file system level I can see a generated >>>> jshint.xml file containing the JSLint errors, a violations/ >>>> violations.xml file and violations/file/<js file name and path>.xml >>>> files but still each file specific link leads to a blank page. >>>> >>>> Any updates on this? Was anyone able to resolve the problem? >>>> >>> >>> I'm still having no luck. I'm using stylecop/fxcop instead of JSLint, >>> but I still have the issue. >>> >>> A few things to note: >>> 1) The build is performance on a slave node (not the master) >>> 2) For FxCop, where the link is to a .cs file, I get the code snippets >>> highlighted with the errors, but I don't get anything about the error text >>> listed above. But if the link is to a class, I get a blank page (with just >>> the violations icon). >>> >>> It's really getting annoying. Is there anywhere else we should be >>> raising this? >>> >>> >>> During the integration of the violations parsers (JSLint, FXCop, etc.) >>> into the warnings plug-in I noticed that the parsers are not serializable. >>> Maybe this is the reason for the behavior. Does the plug-in work on the >>> master? In order to have a working JSLint parser on a slave (for my >>> warnings plug-in) the parsers should be made serializable... >>> >> >> I've just setup a sandpit with a fresh Jenkins installation, and built >> the same job on the MASTER node. Same issue. >> > > I've managed to get some more information (thankfully found some spare > tuits). > > Using PROCMON.exe (from sysinternals), I can see the following: > > 1) Clicking on a *.cs link in the Violations screen gives the following > PATH accesses (all with PATH NOT FOUND): > > %JENKINS_HOME%\war\job\JOB_NAME\violations\file\RELATIVE_PATH_TO_FILENAME > > This path obviously does not exist - why would there be a JOB_NAME folder > under the 'war' directory? The file that it is trying to access appears to > be: > > > %JENKINS_HOME%\jobs\%JOB_NAME%\builds\%BUILD_NAME%\violations\file\%RELATIVE_PATH_TO_FILENAME%.xml > > 2) Clicking on an object name (ie Namespace.ClassName), gives alot of > pathname accesses, trying to locate Namespace.ClassName with .groovy, > .default.groovy and .jelly. > > Hopefully this helps track down the issue. > > Cheers, > Daniel B. >
I'm using Python/Pylint, and also see a blank page when I look at the errors for a particular file. The page contains normal header, footer and sidebar, and displays the violations 'exclamation mark roadsign' icon on the top left, but is otherwise blank It used to work on this same jenkins installation and project, but I'm afraid I'm not sure when or why it stopped working. Possibly a jenkins or violations update, or possibly of course I changed/broke the config somewhere. Any other info is very welcome. Jonathan Hartley
