deploy command doesn't run if heroku's not setup about strider-custom HOT 7 CLOSED

is this still happening after the worker rewrite? it's totally wrong to do this, of course.

from strider-custom.

oh yeah it still is. We bypass deploy if there's no "deploytarget". But we're taking heroku and making it a separate plugin, so that will be fixed.

from strider-custom.

ok, but shouldn't it be a quick fix to always run deploy hooks (not talking about heroku deploy) without heroku config?

from strider-custom.

But we don't allow a TEST_AND_DEPLOY run to happen if there's no
deploy_target set in the DB.
I think we need some way for plugins to broadcast that they can deploy this
project

On Thu, Aug 15, 2013 at 2:56 PM, niallo [email protected] wrote:

ok, but shouldn't it be a quick fix to always run deploy hooks (not
talking about heroku deploy) without heroku config?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-22729770
.

from strider-custom.

+1, my use of strider does internal deploy locally on same machine.

from strider-custom.

fixed by Strider-CD/strider@12c57fc

from strider-custom.

awesome @jaredly !

from strider-custom.