For the sake of completion and information, I'll leave this response here: Everything is solved. In fact, it would have worked all the way if we weren't running 'perlcritic' from inside a sub-folder of the project.
In some point, we changed the script we were using to something like: "cd some/folder/; perlcritic" >From that point on, violations plugin stopped working, since it expects relative paths (for every file) to begin from the root of the workspace. That was the origin of our issue, and the reason why the plugin was printing "no violations found" for every file. Well, that's all. If you ever find yourself struggling with something like this issue, dont forget to check for this. Don't be as dumb as I was , :-) Regards El martes, 15 de julio de 2014 12:26:32 UTC+2, J. M. Castroagudín Silva escribió: > > Hi everyone, > > We are doing some tests using jenkins to periodically run some analysis > (unit testing, code coverage, perlcritic...) on perl projects. > > So far, everything is working quite well: test results are displayed, we > are publishing html reports for code coverage, even the violations plugin > displays a nice summary of perlcritic output... > > But we are facing an annoying issue right there: when clicking on any file > on the 'violations' summary, a page showing the message "No violations > found" is th only thing we get. > > I'm not sure wether this is a known issue, or maybe we are doing something > wrong. > > So, if anyone has any experience using perlcritic + jenkins + violations > plugin, we'll appreciate any hint, tip or advice you could give us. > > Thanks in advance. Regards! > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
