Robin, there's a patch for this somewhere in lighthouse, it's not supported because having noop tasks run when they're not needed defies the purpose of deployment. (Yes, I notice you are doing puppet stuff)
Having noop tasks run as part of a deployment in my opinion makes it less clear how you are deploying your company's most valuable resource, and dilutes the clairty of your deployment process... The patch allows a task to not run if no servers match the role. You may also want to look at using environmental variables on the command line to specify single hosts, or roles. e.g. $ HOSTS=example1.com,example2.com cap deploy $ ROLES=app,web cap deploy -- Lee Hambley Twitter: @leehambley | @capistranorb -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
