From ab01b4c5a7231a2f3febb8f9e367aa010e04cbe9 Mon Sep 17 00:00:00 2001
From: Bryan Stitt <bryan@llamanodes.com>
Date: Fri, 28 Jul 2023 12:42:23 -0700
Subject: [PATCH] no need for REPO_NAME. default will work

---
 Jenkinsfile | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/Jenkinsfile b/Jenkinsfile
index efc5680a..e4c00c48 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -9,12 +9,9 @@ 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}/${REPO_NAME}"
+        REGISTRY="${AWS_ECR_URL}/web3-proxy"
 
         // branch that should get tagged with "latest_$arch" (stable, main, master, etc.)
         LATEST_BRANCH="main"
@@ -22,8 +19,6 @@ pipeline {
         // non-buildkit builds are officially deprecated
         // buildkit is much faster and handles caching much better than the default build process.
         DOCKER_BUILDKIT=1
-
-        GIT_SHORT="${GIT_COMMIT.substring(0,8)}"
     }
     stages {
         stage('build and push') {