-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Add a way to turn off graceful logging #306
Comments
Extension Workflows do not fail for failing extensions and tools to make sure setup can be cross platform as some are platform specific. Currently you can ensure the workflows fail on a project basis by adding a step after For example name: Check mongodb
run: php -r "if(! extension_loaded('mongodb')) {throw new Exception('mongodb not found');}" or fail for multiple extensions, check - #194 (comment) |
Ok, I see the use case, but IMO by default it should fail. It would be great to have something like this:
If the whole point of a job is to test Oracle, and tests for Oracle are in fact skipped because the install silently failed, things are needlessly hard to troubleshoot. |
I'm adding a env variable in next release, when set will change the behaviour to failing by default. |
This should also apply to tools. For example the installation of deployer is current failing due to missing downloads and it took a while to understand what the issue was because the action didn't fail thus the log was collapsed by default. |
@ocean90 Yes, it will work for both extensions and tools |
Thanks a lot! |
Describe the feature
I would like a way to make sure failing to install an extension fails the build
Version
v2
.Underlying issue
Not being able to figure out what is going wrong
Describe alternatives
No alternatives considered
Additional context
See confused people at sonata-project/exporter#394 (comment)
Are you willing to submit a PR?
I'm not planning to, but I guess I could.
The text was updated successfully, but these errors were encountered: