[taler-sandcastle-ng] 02/02: buildbot: use latest tag to simplify deployment

[gnunet]

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

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

commit 9f8a6622485f465538a75a96659df4397b242b5c
Author: Devan Carpenter <devan@taler.net>
AuthorDate: Sat Feb 17 08:50:35 2024 -0500

    buildbot: use latest tag to simplify deployment
    
    We typically just want to update our HEAD deployment in-place, so using
    the same tag ("latest") will simplify the process
---
 contrib/ci/jobs/0-build/build.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/contrib/ci/jobs/0-build/build.sh b/contrib/ci/jobs/0-build/build.sh
index 2f24a32..8a366b8 100755
--- a/contrib/ci/jobs/0-build/build.sh
+++ b/contrib/ci/jobs/0-build/build.sh
@@ -6,5 +6,5 @@ set -exuo pipefail
 mkdir -p /artifacts/sandcastle-ng/${CI_COMMIT_REF} # Variable comes from CI 
environment
 podman tag taler-base-all:latest taler-base-all:${CI_COMMIT_REF}
 podman save \
-       -o 
/artifacts/sandcastle-ng/${CI_COMMIT_REF}/taler-base-all-${CI_COMMIT_REF}.tar \
-       taler-base-all:${CI_COMMIT_REF}
+       -o /artifacts/sandcastle-ng/${CI_COMMIT_REF}/taler-base-all.tar \
+       taler-base-all:latest

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