-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thoughts on failures if ruleset fails #2
Comments
Hey James, I'm on the road, so I can't look into it deeply. It should only ignore the fail on exit code 2, which is documented on http://phpmd.org/documentation/index.html#exit-codes Because md-violations are no criteria for me to fail it, I only want to get them documented. But I could change that to a configuration setting… would that help you? Regards |
Cool - understand where you are coming from with this. I've seen your pull request from other repo's for grunt-phpcs etc. I'll see if I can keep it all in sync as this makes sense. Cheers, James |
I would like to see at least some warning issued to the output. This way I could configure my CI server (Jenkins) to parse the build output for that string and set my build to unstable. |
+1 I would also try to use this task for CI and in current state it's imposible. |
Indeed I would… |
Ok i will prepare something on weekend. I think it would be best to add option |
Yes, sounds great… |
Hey @adam187, thanks for the reminder… |
Hi,
Currently the task doesn't fail if the phpmd identifies issues. What are your thoughts on making the task fail?
Cheers,
James
The text was updated successfully, but these errors were encountered: