-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
Job is executed at a Windows Server 2008 Slave running Hudson Slave as a Service using an account with local admin privilegues. The Hudson master is located on an Ubuntu 10.04 machine.
Hi!
We use the Violations plugin to capture StyleCop warnings. But we
can't click the links in the Violations plugin to see our StyleCop
violations, however it does work for our FxCop violations and our
StyleCop violations are at least noticed even though it doesn't seem
to work as intended.
In case this isn't a bug we're posting it here first. To the details:
The plugins we use: http://i.imgur.com/m0rFx.png
See the violations report for build 4: http://i.imgur.com/wRJtt.png
The last FxCop violation works, and has the link:
http://ci.devel.siteseeker.se:8080/job/dotnet/violations/file/siteseeker.web.webforms.dll
The only file in violation of a StyleCop rule has the link:
http://ci.devel.siteseeker.se:8080/job/dotnet/violations/file/SiteSeeker.CoreTest%5Cobj%5CRelease%5CIntegrationTests.cs
The StyleCop violation link doesn't work. It gives us an ERROR: 400
Bad Request back: http://i.imgur.com/9qAdT.png
Both of them link to the master server which is running Ubuntu and
both of them execute on the Windows slave.
This is how our job configuration looks: http://i.imgur.com/St2zu.png
And this is the console output for that job: http://i.imgur.com/ZogTg.png
I have also posted this in a mail thread which might be of some value. The URL is in the ticket.
The violations plugin is deprecated. It has an unresolved security vulnerability. The last commit to the source code repository was over 7 years ago. Closing the issue as "Won't fix"