Alex

Can you please explain a bit more on your usecase? I agree, that when attempt is made to get current release path, when no releases are made (or even folder...

According to documentation what happens is this: 1. take all connections (4 in your case if you have 1 stage only) 2. run them in parallel So the effect of...

The documentation (see http://rocketeer.autopergamene.eu/#/docs/docs/II-Concepts/Tasks) says, that tasks would be autoloaded from `.rocketeer/tasks` folder only. This must be an error of some kind. I suspect, that other folders that can be...

This is because default strategy for dependency management is `Polyglot`. You either need to disable dependency management or set it to only one you need (e.g. `npm`).

You can run tests in a before hook to the symlink and this way they can block actual symlink, but not sure if that will stop whole deploy.

I don't know about Windows, because I'm not a Windows user. But I can suggest better alternative to particular lines used in that hook. > $test = $task->run('phpunit -c '.$task->releasesManager->getCurrentReleasePath('tests/phpunit.xml'));...

If you did a rollback, then why you're calling `update` at all? The `update` only purpose is to make a deploy without creating new release. The `rollback` is supposed to...

Looking at documentation this is not possible. The servers array in the connection configuration is processed either sequentially (one after another) or in parallel. The parallel execution however doesn't guarantee...

The https://docs.ansible.com/ansible/deploy_helper_module.html might help if you go that way.

Sorry for getting back to this only now, but I believe #201, that I've created recently might offer a way to solve this problem. This however will create a BC...