Open dmaphy opened 8 years ago
Oh, and one additional thing I forgot to mention: this issue is not present when calling the rocketeer deploy
command with --parallel
. This isn't an option for our deployment, though. Since it would lead to suboptimal situations as well when having all php5-fpm.services down at once.
Having the same problem here. Did you find out how to solve it?
No, unfortunately not. Currently we're living with the --parallel
switch as a workaround for this.
There is an issue with the hooks when running a deploy command for more than just one server. Lets say, for example, there are the following connections defined in
config.php
:The
hooks.php
contains some systemd commands to stop services before deployment and start services after deployment:Those commands are allowed for
appuser
to be executed via sudo on every server and this basically works when running a simple deploy command to deploy stuff on one server:rocketeer deploy --on="testing" --branch="master"
The issue takes effect as soon as you try to run this in any form for multiple of the above mentioned connections (or the production connection which contains four servers), e.g.:
rocketeer deploy --on="testing,integration" --branch="master"
You then get something like the following output:
Now, note that, fully independent of the connstellation or what servers you list, from the second server on always this happens before the deploy:
This leads to two issues:
hooks.php
just do not work from the second server onFor us, this results in old APC caches which have not been cleared because PHP5-FPM has not been restarted. This is, in particular, suboptimal when deploying to the production connection.
Any ideas how to solve this?
Thanks very much in advance & Best Regards, Dominic