fix(deploy): catch Exception instead of RuntimeError

In the deploy function Exception is caught, problem logged and then re-raised. Best to catch Exception as well to clean up the release object around it

Potentially affects the following tickets:
#410, #319, #187, #320

Author: helgi

rootfs/api/models/build.py

@@ -43,7 +43,7 @@ def create(self, user, *args, **kwargs):
         try:
             self.app.deploy(user, new_release)
             return new_release
-        except RuntimeError:
+        except Exception:
             if 'new_release' in locals():
                 new_release.delete()
             raise

rootfs/api/models/release.py

@@ -115,7 +115,7 @@ def rollback(self, user, version):
             if self.build is not None:
                 self.app.deploy(user, new_release)
             return new_release
-        except RuntimeError:
+        except Exception:
             if 'new_release' in locals():
                 new_release.delete()
             raise

rootfs/api/views.py

@@ -316,7 +316,7 @@ def post_save(self, config):
             # It's possible to set config values before a build
             if self.release.build is not None:
                 config.app.deploy(self.request.user, self.release)
-        except RuntimeError:
+        except Exception:
             self.release.delete()
             raise