-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Configurability of timeout for default recipes #1256
Comments
Yes, it's because of https://github.com/deployphp/deployer/blob/master/src/Utility/ProcessRunner.php#L27 |
I wouldn't hack it with fast solution, the timeout is there for a reason. In worst case scenario I can fork it and have it with a higher limit, until we figure out how to do it properly :). I haven't look at the internals so maybe I will try to come up with some solution. |
Maybe create one config option for default timeout: set('default_timeout', 360); |
+1 Would be great to have this. Currently my Magento 2 deployments can run into problems with lengthy |
+1 |
1 similar comment
+1 |
However, you can override it for a single task like so:
|
Done! Will be in v6. |
Description
My current issue is that when the task runs for more than 300 seconds, it throws an Exception. However my
composer install
takes longer (due to various reasons that are valid) and I have no possibility to raise the 300 second limit other than editingsrc/Utility/ProcessRunner.php
directly. I'd like to be able to state this within mydeploy.php
file, preferably for each task separately.Steps to reproduce
Content of
deploy.php
Output log
The text was updated successfully, but these errors were encountered: