Broken recipes with Deployer 5.x about recipes HOT 24 CLOSED

recipes v5 once released will work with deployer 4.x

I dont think so)) v5 will work with v5

from recipes.

Really hard, some help will be nice)

from recipes.

Hi,
I have fixed:

• Slack recipe (PR #131), but may be conflicting with other pending PR about Slack.
• Rollbar recipe (PR #133)

(@antonmedv, your work is just super awesome. Congrats)

from recipes.

I noticed that the rsync recipe is also broken. It internally uses a call to ::getServer(), but it seems the API has changed to something like "hosts". Are there any plans to bring the recipes to version 5 as well?

from recipes.

Now recipe not quite ready for v5 of deployer. Now i'm in process of refactoring entire recipe project and it may be broken. But i hope to find enough time to ship it faster.

from recipes.

from recipes.

Yeah versioning is great and makes sense, I was more wondering if master here was being kept up to date with changes in Deployer master as it's hard to work/test deployer beta while recipes are broken.

It's no problem anyway I'll override while I'm working on things and if I finish it before someone else I'll PR changes 👍

from recipes.

from recipes.

I'll PR changes

👍🏻

from recipes.

I noticed some recipes indeed breaking after updating to Deployer 5.0.0. At least slack and bugsnag recipes return the following exception. Seems like the get('stages') is gone in v5. This seems to affect a quite of other recipes as well.

  [Deployer\Exception\ConfigurationException]        
  Configuration parameter `stages` does not exists.  
                                                     
Exception trace:
 () at phar:///usr/local/bin/dep/src/Configuration/Configuration.php:93
 Deployer\Configuration\Configuration->get() at phar:///usr/local/bin/dep/src/functions.php:517
 Deployer\get() at /home/lasleh/Code/digital-distribution/vendor/deployer/recipes/bugsnag.php:16
 Deployer\Deployer::Deployer\{closure}() at n/a:n/a
 call_user_func() at phar:///usr/local/bin/dep/src/Task/Task.php:82
 Deployer\Task\Task->run() at phar:///usr/local/bin/dep/src/Executor/SeriesExecutor.php:63
 Deployer\Executor\SeriesExecutor->run() at phar:///usr/local/bin/dep/src/Console/TaskCommand.php:131
 Deployer\Console\TaskCommand->execute() at phar:///usr/local/bin/dep/vendor/symfony/console/Command/Command.php:265
 Symfony\Component\Console\Command\Command->run() at phar:///usr/local/bin/dep/vendor/symfony/console/Application.php:826
 Symfony\Component\Console\Application->doRunCommand() at phar:///usr/local/bin/dep/src/Console/Application.php:132
 Deployer\Console\Application->doRunCommand() at phar:///usr/local/bin/dep/vendor/symfony/console/Application.php:189
 Symfony\Component\Console\Application->doRun() at phar:///usr/local/bin/dep/vendor/symfony/console/Application.php:120
 Symfony\Component\Console\Application->run() at phar:///usr/local/bin/dep/src/Deployer.php:315
 Deployer\Deployer::run() at phar:///usr/local/bin/dep/bin/dep:110
 require() at /usr/local/bin/dep:4

deploy [-p|--parallel] [-l|--limit LIMIT] [--no-hooks] [--log LOG] [--roles ROLES] [--hosts HOSTS] [--] [<stage>]

from recipes.

Yes, i'm working on rewriting whole recipes repository. Hope finish at weekends. Also making a lot of refactoring by the way. Recipes now – trash.

from recipes.

from recipes.

@fdemiramon thanks)

from recipes.

@antonmedv said he'll fix things. I believe. Or I'll fix some I use once I get a handful of fre time. Not now though, pesky human condition needs sleep.

from recipes.

I'll try to find some free time on this weekend) Open source takes a lot of time

from recipes.

Also receiving this error when using BugSnag recipie

[Deployer\Exception\ConfigurationException]
Configuration parameter `stages` does not exists.

from recipes.

Yep, actually I'm planning to release Deployer v6 and Recipes v6 and after that work on Recipes v5 for Deployer v5 (If some one willing to help it will be much faster).

from recipes.

I don't see the point of investing time for v5 if you have a v6 set to be released soon. Are there any lifecycle or support issues that make it necessary?

from recipes.

Deployer 6 and Recipes 6 already released. Then I found time I'll will backport this to v5.

from recipes.

Maybe someone wants to help me with recipes? And clear it up for v5?

from recipes.

maybe we should add to recipes composer.json requirement for a specific deployer version. this repo already depends and uses code form dpeloyer repo but we don't specify it as a dependency, not sure why. It would help a lot to keep track of which deployer version recipes support and visa versa also would be easier to release changes to both projects without requiring to release a major version for a change in deployer code that a recipe depends on in a new version

from recipes.

Problem with it, deployer can be installed via phar and not through composer.

from recipes.

ah true, but recipes can't be used as standalone they still depend on deployer, so maybe require-dev then, at least we would get autocompletion for deployer code

from recipes.

Make sense

from recipes.