Skip to content
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

When deploy fails and --activate succeeds, a success code is returned #327

Closed
joshsmith opened this issue Dec 14, 2015 · 9 comments
Closed
Labels

Comments

@joshsmith
Copy link

It appears that when a deploy fails but activation succeeds with the --activate command, the return is a success code for the activation. On my CI server this looks to me like a false positive.

Is this the expected behavior? Or should the whole thing fail? My guess is you don't even want to proceed with the activation in the event of a failing deploy.

@ghedamat
Copy link
Collaborator

@joshsmith it should definitely fail and not activate

I don't remember seeing this one, but thanks for reporting, we'll try to reproduce it and report back

@ghedamat ghedamat added the bug label Dec 14, 2015
@joshsmith
Copy link
Author

@ghedamat I can tell you exactly what it failed on: I had provided a username (which is included by default in Redis Cloud's URL on Heroku). This username fails with the same error seen here: ember-cli-deploy/ember-cli-deploy-lightning-pack#9

While the username is a whole separate issue, I planned to take the URL dynamically from Heroku with my API key and use that for the Redis URL. Given that this URL could change, I'd prefer that over hamfisting it manually into my CI's env.

@ghedamat
Copy link
Collaborator

@joshsmith I think I've been able to reproduce, looks like the redis plugin is swallowing the error and preventing the pipeline from aborting, will investigate more soon

@ghedamat
Copy link
Collaborator

ok, here's the current status of my investigation

this is a problem related ONLY to ember-cli-deploy-redis

with the current version of then-redis that we're using in that plugin, when redis returns a parse error the redis library used doesn't seem to send the proper error event, because of that then-redisdoesn't receive it and we don't get a rejected promise, so we don't abort the pipeline.

It looks like then-redis is not maintained anymore https://github.com/mjackson/then-redis/issues/51 and that the current consensus is to use node-redis directly with bluebird

https://github.com/NodeRedis/node_redis#promises

I guess if I'm right and this is the problem we'll need a good PR to ember-cli-deploy-redis

/cc @achambers @lukemelia @joshsmith

@achambers
Copy link
Member

Thanks for investigating @ghedamat

@lukemelia
Copy link
Contributor

@ghedamat should we move this to ember-cli-deploy/ember-cli-deploy-redis?

@ghedamat
Copy link
Collaborator

@lukemelia I think so

@jordanyee
Copy link

For anyone else looking: this was moved to ember-cli-deploy/ember-cli-deploy-redis#36.

@achambers
Copy link
Member

Closing this issue now in favour of ember-cli-deploy/ember-cli-deploy-redis/issues/51

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants