You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2019. It is now read-only.
Maybe there is a good reason at that (impossibility to output well formed XML via Grunt ?), or maybe I missed something. What do you think about that ?
I could try to implement this feature, if feasible / possible.
The text was updated successfully, but these errors were encountered:
I played a little yesterday, I managed to generate a jUnit xml sekeleton on standard output.
But upon further research, I think it may be the same problematic as grunt-contrib-jshint : gruntjs/grunt-contrib-jshint#8
For tight integration of tools like jsHint, jsValidate with an CI platform (Hudson / Jenkins), grunt tasks may not be the response.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm currently integrating front-end build tasks on a CI server. The CI manager would want a JUnitXML as output.
I've read a mention about that in http://ariya.ofilabs.com/2012/10/javascript-validator-with-esprima.html
I tried to pass a
esprimaOptions: {format:'junit'}
to the jsvalidate task, but it doesn't seem to work.In https://github.com/ariya/grunt-jsvalidate/blob/master/tasks/jsvalidate.js the esprimaOptions doesn't seem to be used.
Maybe there is a good reason at that (impossibility to output well formed XML via Grunt ?), or maybe I missed something. What do you think about that ?
I could try to implement this feature, if feasible / possible.
The text was updated successfully, but these errors were encountered: