taler-deployment

commit 7f950d9ad4d320a82fa0edf2ec90c21e98e2eebf
parent 938cefcf648d03bdd307071cf4acb6c17f469a81
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Wed, 22 Jun 2016 12:34:45 +0200

removing blue-green picking logic
from shell script, as now is buildbot who picks up the non active party

Diffstat:
M
taler-build/switch_active.sh
 | 
26
++++----------------------

1 file changed, 4 insertions(+), 22 deletions(-)
diff --git a/taler-build/switch_active.sh b/taler-build/switch_active.sh
@@ -1,31 +1,13 @@
 #!/bin/bash
 
-# Build all Taler components (currently only the wallet build+test is
-# not supported) 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,
+# 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
 
-whoami
-
-# figure out which is the inactive
-ACTIVE=$(readlink /home/test/sockets | awk -F/ '{print $3}')
-
-# exit if active
-if [[ $(whoami) == $ACTIVE ]]; then
-  exit
-fi
-
-if [[ 'test-green' == $ACTIVE ]]; then
-  INACTIVE='test-blue'
-else
-  INACTIVE='test-green'
-fi
-
-# build and restart
-# FIXME calling 'make check' before switching still missing
 if ! taler-deployment-build; then
   echo "Failed to rebuild, not switching"
 else