-
Notifications
You must be signed in to change notification settings - Fork 34
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
scapegoat failOnError := false #65
Comments
Seems like there is an option to allow some warnings/errors before failing the build, but I could not make it work with 1.0.5. See issue #60 |
Same here, couldn't make it work. |
I think this is related to #72 . |
Any news on it ? Thanks! |
It would be great to have this in place. Any news regarding this? Any workaround? |
If you want to upload the report to Sonar you can change the level of Error inspections to Warning. Doing this the run don't fail (even with warnings) and given that what you really want is to see the quality profile of Sonar not the real scapegoat report it "solves the problem". You can add to you project settings Is not the best option but it works at least with Sonar. Anyway as you say, it would be great to have this |
Another workaround is to do |
I can see the situation haven't changed anything. |
Hi,
Is there any way to do NOT fail if an error is found while scapegoat task is executed?
Since I have to upload the scapegoat-report to sonar, wouldn't be better to have this option?
Do you have some example in order to go ahead even if errors are found?
Thanks in advance.
The text was updated successfully, but these errors were encountered: