gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-deployment] branch master updated: buildbot: to be pythonic one m


From: gnunet
Subject: [taler-deployment] branch master updated: buildbot: to be pythonic one must use getuid
Date: Sat, 17 Feb 2024 05:50:10 +0100

This is an automated email from the git hooks/post-receive script.

devan-carpenter pushed a commit to branch master
in repository deployment.

The following commit(s) were added to refs/heads/master by this push:
     new b2f649b  buildbot: to be pythonic one must use getuid
b2f649b is described below

commit b2f649b1a94477322438d069526977c452a717e7
Author: Devan Carpenter <devan@taler.net>
AuthorDate: Fri Feb 16 23:49:14 2024 -0500

    buildbot: to be pythonic one must use getuid
    
    os.getenv will not work for retrieving "$UID", as it is a built-in shell
    variable. luckily we have "os.getuid" for this purpose.
---
 buildbot/master.cfg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/buildbot/master.cfg b/buildbot/master.cfg
index 7e6c075..559bf06 100644
--- a/buildbot/master.cfg
+++ b/buildbot/master.cfg
@@ -230,7 +230,7 @@ def container_add_step(HALT_ON_FAILURE,
                                            "--env", 
util.Interpolate("CI_GIT_BRANCH=%(src::branch)s"),
                                            "--volume", f"{WORK_DIR}:/workdir",
                                            "--volume", 
"/home/container-worker/container_artifacts:/artifacts",
-                                           "--volume", 
f"/run/user/{os.environ.get('UID')}/podman/podman.sock:/run/podman/podman.sock",
+                                           "--volume", 
f"/run/user/{os.getuid()}/podman/podman.sock:/run/podman/podman.sock",
                                            "--security-opt", "label=disable",
                                            "--workdir", "/workdir",
                                            CONTAINER_NAME, jobCmd],

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]