[no-relnote] Override publishing path

The project or group CI variables have a higher precedence than
variables at a job level. This means that the dummy publishing job
also publishes a "real" MR.

This change ensures that we explicitly override the global value.

Signed-off-by: Evan Lezar <[email protected]>

Author: elezar

.nvidia-ci.yml

@@ -252,13 +252,17 @@ push-images-to-staging:
     PROJECT_NAME: "nvidia-container-toolkit"
   before_script:
     - |
+      if [ -n "$OVERRIDE_PUBLISHING_PROJECT_PATH" ]; then
+        NGC_PUBLISHING_PROJECT_PATH=${OVERRIDE_PUBLISHING_PROJECT_PATH}
+      fi
+
       if [ -z "$NGC_PUBLISHING_PROJECT_PATH" ]; then
         echo "NGC_PUBLISHING_PROJECT_PATH not set"
         exit 1
-      else
-        echo "publishing to ${NGC_PUBLISHING_PROJECT_PATH}"
       fi
 
+      echo "publishing to ${NGC_PUBLISHING_PROJECT_PATH}"
+
       rm -f ${VERSION_FILE}
       echo "${IN_IMAGE_TAG} ${OUT_IMAGE_TAG}" >> ${VERSION_FILE}
       echo "${IN_IMAGE_TAG}-packaging ${OUT_IMAGE_TAG}-packaging" >> ${VERSION_FILE}
@@ -284,7 +288,7 @@ publish-images-dummy:
   extends:
     - .publish-images
   variables:
-    NGC_PUBLISHING_PROJECT_PATH: dl/container-dev/ngc-automation
+    OVERRIDE_PUBLISHING_PROJECT_PATH: dl/container-dev/ngc-automation
     OUT_IMAGE_TAG: "publish-${CI_COMMIT_SHORT_SHA}"
   rules:
     - if: $CI_COMMIT_TAG == null || $CI_COMMIT_TAG == ""