Le 15 déc. 2014 à 12:17, Norbert Hartl a écrit : > >> 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/ >> >> 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.
The missing thing is an output for the Jenkins Violations plugin (https://wiki.jenkins-ci.org/display/JENKINS/Violations). We could have our own type (critics) or just re-use one (ex: pmd). I also wanted to do that but did not get the time yet. I also want that critics are checked in the same time as tests in jenkins jobs.
smime.p7s
Description: S/MIME cryptographic signature
