Skip to content
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

Closed
jrcryer opened this issue Jul 27, 2013 · 10 comments
Closed

Thoughts on failures if ruleset fails #2

jrcryer opened this issue Jul 27, 2013 · 10 comments

Comments

@jrcryer
Copy link
Contributor

jrcryer commented Jul 27, 2013

Hi,

Currently the task doesn't fail if the phpmd identifies issues. What are your thoughts on making the task fail?

Cheers,

James

@alappe
Copy link
Owner

alappe commented Aug 5, 2013

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
Andy

@jrcryer
Copy link
Contributor Author

jrcryer commented Aug 5, 2013

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

@joerx
Copy link

joerx commented May 19, 2014

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.

@adam187
Copy link
Contributor

adam187 commented Aug 26, 2014

+1 I would also try to use this task for CI and in current state it's imposible.
I can prepere some pull request with additional configuration option if you don't have time for it @alappe.

@jrcryer
Copy link
Contributor Author

jrcryer commented Aug 26, 2014

@joerx and @adam187 - PRs sound excellent. Sure @alappe would appreciate it!

@alappe
Copy link
Owner

alappe commented Aug 26, 2014

Indeed I would…

@adam187
Copy link
Contributor

adam187 commented Aug 27, 2014

Ok i will prepare something on weekend.

I think it would be best to add option minErrorLevel with default value of 2 so it won't break BC and when you change it to 1 it will trigger fatal for error code 1 and 2 from phpmd instead only form 2. What do you think about that @alappe ?

@alappe
Copy link
Owner

alappe commented Aug 27, 2014

Yes, sounds great…

@adam187
Copy link
Contributor

adam187 commented Sep 17, 2014

@alappe Any news with this :) ?
My PR is ready for a long time #5

alappe pushed a commit that referenced this issue Sep 18, 2014
@alappe
Copy link
Owner

alappe commented Sep 18, 2014

Hey @adam187, thanks for the reminder…

@alappe alappe closed this as completed Sep 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants