From 89bbd0021574b12538e086e2956561e9888f000c Mon Sep 17 00:00:00 2001
From: Bryan Stitt <bryan@llamanodes.com>
Date: Fri, 28 Jul 2023 11:34:39 -0700
Subject: [PATCH] add REPO_NAME variable

---
 Jenkinsfile | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/Jenkinsfile b/Jenkinsfile
index 39a74578..efc5680a 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -9,9 +9,12 @@ pipeline {
         ansiColor('xterm')
     }
     environment {
+        // TODO: can we just use jenkin's PROJECT_NAME? I think that might cause problems with things in the provisioning repo
+        REPO_NAME="web3-proxy"
+
         // AWS_ECR_URL needs to be set in jenkin's config.
         // AWS_ECR_URL could really be any docker registry. we just use ECR so that we don't have to manage it
-        REGISTRY="${AWS_ECR_URL}/web3-proxy"
+        REGISTRY="${AWS_ECR_URL}/${REPO_NAME}"
 
         // branch that should get tagged with "latest_$arch" (stable, main, master, etc.)
         LATEST_BRANCH="main"