-
Notifications
You must be signed in to change notification settings - Fork 63
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
Cache warmup SSH commands being executed multiple times per host #122
Comments
Hello, this is indeed a bug, so either commit 5f0bf73 should be reverted or the additional |
@kissifrot I think it would make more sense to revert the commit as opposed to removing the However, it would seem that "execute should be wrapped in an 'on' scope" so we may be stuck with removing the |
…le times when multiple servers are defined
This is still happening, on both v1.0.0 ánd v2.0.0... Is there any fix for this? I have only 4 servers configured, but the cache:warmup is triggered a whopping 11 times! 😓. These are the configures servers. server "10.0.0.5",
user: "deploy",
roles: %w{web},
primary: true
server "10.0.1.5",
user: "deploy",
roles: %w{web}
server "10.0.0.8",
user: "deploy",
roles: %w{web}
server "10.0.0.10",
user: "deploy",
roles: %w{ocpp},
primary: true |
After updating to Symfony 4.4 and migrating to v2 of this gem I was reviewing deploy logs and noticed that the
symfony:cache:warmup
task was running the SSH command itself multiple times per server. I deploy to 9 servers, and the command looks like it's running 81 times, 9 per server.The
symfony_console
call in that task is wrapped in anon
:https://github.com/capistrano/symfony/blob/master/lib/capistrano/tasks/symfony.rake#L31
Then the
symfony_console
function itself contains anotheron
:https://github.com/capistrano/symfony/blob/master/lib/capistrano/dsl/symfony.rb#L42
So it looks like it's saying "on each server, run the cache warmup command on each server". Am I misunderstanding this and I have a different issue? This explanation seems to fit the results I'm seeing.
The text was updated successfully, but these errors were encountered: