taler-deployment

commit b609e52778e12d24cfb1cba7fcad2540aaa0707c
parent 7e559340576130b30715ce2c45b766eae959f75f
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Tue,  7 Mar 2017 14:27:14 +0100

Restarting ARM via buildbot.

Diffstat:
D
taler-build/switch_active.sh
 | 
22
----------------------
M
taler-build/switch_bluegreen.sh
 | 
1
+

2 files changed, 1 insertion(+), 22 deletions(-)
diff --git a/taler-build/switch_active.sh b/taler-build/switch_active.sh
@@ -1,22 +0,0 @@
-#!/bin/bash
-
-# Build all Taler components for the non active party
-# of blue-green, and switch to it whenever compilation
-# and testing succeed. The script is not portable to
-# system using different usernames and directories,
-# respect to taler.net, for blue-green deployments
-
-set -eu
-
-if ! taler-deployment-build > build.log 2>&1; then
-  echo "Failed to rebuild, not switching"
-  if test "$1" = "--notify"; then
-    mail -s "[Taler build] $(date)" build-failure@taler.net < build.log
-  fi
-  exit 1
-else
-  echo "Successfully built, switching"
-  ln -fs -T /home/$(whoami)/sockets /home/test/sockets
-fi
-
-taler-deployment-restart
diff --git a/taler-build/switch_bluegreen.sh b/taler-build/switch_bluegreen.sh
@@ -13,4 +13,5 @@ if sudo -u $nonactive \
 
   echo "Switching to ${nonactive}."
   sudo -u test bash -c "cd /home/test; ./ln-${nonactive}.sh"
+  sudo -u $nonactive bash -c 'cd $HOME; . activate; taler-deployment-restart'
 fi