taler-deployment

commit 67fc7d20de3696e97ece0e225cf4cbb0406932b2
parent 9b4ea0c8c0b4201b6d40694539cb0727ad6f013d
Author: ms <ms@taler.net>
Date:   Fri, 25 Jun 2021 16:08:46 +0200

Tip reserve deployment.

The creation of a tip reserve goes as a Buildbot step,
along of being a SystemD job as well.  This way, we avoid
problematic time gaps between the codebase compilation
and the intervention of SystemD in the activation of a
tip reserve.

Diffstat:
A
buildbot/create_tip_reserve.sh
 | 
7
+++++++
M
buildbot/master.cfg
 | 
12
++++++++++++

2 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/buildbot/create_tip_reserve.sh b/buildbot/create_tip_reserve.sh
@@ -0,0 +1,7 @@
+#!/usr/bin/env bash
+
+# Step for the BUILD_FACTORY running the 'test.taler.net' site.
+set -eu
+
+source "${HOME}/activate"
+taler-deployment-config-tips
diff --git a/buildbot/master.cfg b/buildbot/master.cfg
@@ -1056,6 +1056,18 @@ BUILD_FACTORY.addStep(
     )
 )
 
+BUILD_FACTORY.addStep(
+    ShellCommand(
+        name="activate tip reserve",
+        description="Instruct the merchant to pay and authorize the tip reserve.",
+        descriptionDone="The tip reserve got payed and authorized.",
+        command=["./create_tip_reserve.sh"],
+        workdir="../../deployment/buildbot",
+        haltOnFailure=True,
+        env={'DEPLOYMENT': "test"}
+    )
+)
+
 BUILDERS.append(util.BuilderConfig(
     name="test-builder", workernames=["test-worker"], factory=BUILD_FACTORY
 ))