[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-deployment] branch master updated: invalidating buildmaster worke
From: |
gnunet |
Subject: |
[taler-deployment] branch master updated: invalidating buildmaster worker |
Date: |
Thu, 10 Sep 2020 12:45:26 +0200 |
This is an automated email from the git hooks/post-receive script.
ms pushed a commit to branch master
in repository deployment.
The following commit(s) were added to refs/heads/master by this push:
new f5b46f4 invalidating buildmaster worker
f5b46f4 is described below
commit f5b46f407175e01f661637c2e1d6351a0974f474
Author: MS <ms@taler.net>
AuthorDate: Thu Sep 10 12:45:16 2020 +0200
invalidating buildmaster worker
---
buildbot/master.cfg | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/buildbot/master.cfg b/buildbot/master.cfg
index 06b7e29..cfb8091 100644
--- a/buildbot/master.cfg
+++ b/buildbot/master.cfg
@@ -391,7 +391,13 @@ BUILDMASTER_FACTORY.addStep(
name="restart buildmaster",
description="trigger buildmaster restart with new configuration",
descriptionDone="Buildmaster updated",
- command=["systemctl", "--user", "restart", "buildbot-master"],
+ # This worker has two problems:
+ # 1 "buildbot reconfig" doesn't work with a systemd-managed
+ # master, because it either doesn't generate a twistd.pid
+ # file or it generates a _invalid_ one.
+ # 2 restarting the master has the problem of _cancelling_
+ # the current builds (including this one)
+ command=["false"],
workdir="../../master/"
)
)
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-deployment] branch master updated: invalidating buildmaster worker,
gnunet <=