Why does the Checkstyle page viewer need the full paths? All it needs to do
is output the given file name (regardless of whether it exists or not) and
the warnings/errors for those files.
If it wants to use the paths to display samples of the code, how does that
work for old builds? Files could have been moved by then, or Jenkins might
be installed in a different location etc. Unless it caches the samples
during the build this doesn't scale very well.
And besides, when looking at the build page in Jenkins I don't want to see
"/var/lib/jenkins/jobs/Job-Name/workspace" in front of it, just the
relevant path names for the project.
-- Tem Corner
On Monday, November 5, 2012 4:50:27 PM UTC+1, Bertrand Tornil wrote:
>
> Hi
>
> I have something working, here :
>
> In the generated jshint.xml file, the full path is missing into the "name"
> attribute of each tag <file /> .
>
> For instance :
>
> <?xml version="1.0" encoding="utf-8"?>
> <jslint>
> <file name="*tcg/static/app/app.js*">
> <issue line="16" char="16" reason="Extra comma." evidence=" workers:
> {}," />
> ...
>
> You need to add the full path : in my case something like
>
> <?xml version="1.0" encoding="utf-8"?>
> <jslint>
> <file name="*/Users/bobuss/Projects/tcg-concept/tcg/static/app/app.js*">
> <issue line="16" char="16" reason="Extra comma." evidence=" workers:
> {}," />
>
>
> I was able to fix it with a sed oneliner :
>
> sed -E 's?<file name="(.*)\?">?<file name="'`pwd`'/\1">?' jshint.xml >
> jshint-proper.xml
>
>
> Then adapt your job configuration to use the jshint-proper file instead of
> the jshint.xml
>
>
> Hope it will help,
>
> B.
>
>
>
> Le vendredi 3 février 2012 18:33:58 UTC+1, Bob Koertge a écrit :
>>
>> I cannot seem to get detailed infomration on my errors with JSLint and
>> violations. Here is some screenshots
>> http://screencast.com/t/Vu6vo2y9 -> I get the overall results, but
>> clicking any of the .js file links leads to a blank page!....
>> http://screencast.com/t/LHM09UYw9ruf
>>
>> Anyone have any ideas?
>>
>
