> Am 15.12.2014 um 12:05 schrieb Yuriy Tymchuk <yuriy.tymc...@me.com>: > > Well… there is this job: > https://ci.inria.fr/pharo/view/3.0-Analysis/job/Pharo-3.0-CodeCritics/plot/Pharo%20(Kernel%20only)%20analysis/ > > <https://ci.inria.fr/pharo/view/3.0-Analysis/job/Pharo-3.0-CodeCritics/plot/Pharo%20(Kernel%20only)%20analysis/> > > It’s a bit complicated, but in Pharo4 rule checking got much easier, so you > can script something buy yourself, or I can help you. The main question is > what do you want to obtain? > Back then there was a mapping from lint warnings and errors to a checkstyle format file which can be feeded into the checkstyle plugin on jenkins. That would be fine. I wouldn't be sad if the categories of lint rules could be seen in the jenkins graph. That might be possible to do but that is hard to configure on the job.
Norbert > Uko > >> On 15 Dec 2014, at 11:49, Norbert Hartl <norb...@hartl.name >> <mailto:norb...@hartl.name>> wrote: >> >> What are the best options at the moment to see the output of lint results in >> jenkins? Is there something to use with checkstyle or any other tools? >> I know the repo on >> >> http://smalltalkhub.com/mc/ClementBera/code-critic-jenkins/main >> <http://smalltalkhub.com/mc/ClementBera/code-critic-jenkins/main> >> >> but I cannot figure out what is the best way to use it. >> >> thanks, >> >> Norbert >> >
