Mike Henke

Yes. Most inspection tools create an xml file Jenkins reads and uses for graphs & other integration.

here is a snippet from the jslint inspection xml file created: < jslint> < file name="\xxx\servers\xxx\cfusion.ear\cfusion.war\tests\inspection\Buttons.js"> < issue line="1" char="9" reason="Expected 'var' at column 1, not column 9." evidence=" var...

here are some inspections I created for cfml projects https://github.com/mhenke/Cloudy-With-A-Chance-Of-Tests here are screenshots of the results in jenkins http://henke.ws/post.cfm/cloudy-with-a-chance-of-tests-screenshots

it is an easy 7 steps as described above, lol :-)

They are different plugins for jenkins. qpscanner might fit better as a violation but I don't see an easy way to add a new voilation type. Guess if we want...

k. i think in your commit just add #12 (pound sign and ticket number) then github issues will match the commit to the task.

Seems like below query by cfquery looping. reading the ticket seems this is specific to queries.

Hmm seems like that section is missing cfoutput of a query also.

Maybe that section should be like this ### Looping Through Results blah #### CFOutput blah, blah #### CFLoop blah, blah

Sure sounds fine :-)