Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Catch ssh errors #12

Open
xendk opened this issue Feb 14, 2014 · 3 comments
Open

Catch ssh errors #12

xendk opened this issue Feb 14, 2014 · 3 comments
Labels

Comments

@xendk
Copy link
Member

xendk commented Feb 14, 2014

If ssh fails, the commands fail, but it's not immediately obvious that it's a ssh problem. Usually it's the sanity check that fails, but it claims that the repo is not clean.

As long as sanity check is always the first action, it could be checked there. If it's not, the handling should be in Action::sh().

@xendk xendk added the invalid label Feb 14, 2014
@xendk xendk removed the invalid label Feb 27, 2014
@xendk xendk removed the 1 - Ready label Jul 30, 2014
@xendk xendk added bug and removed bug labels Sep 22, 2014
@arnested
Copy link
Member

arnested commented Dec 7, 2016

Or have a SshCheck action as the first action?

@xendk
Copy link
Member Author

xendk commented Dec 8, 2016

How does that go with local deployments?

@arnested
Copy link
Member

arnested commented Dec 8, 2016 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

2 participants