function was renamed

Author: mihxil

README.adoc

@@ -23,7 +23,7 @@ An advantage of this approach is that it can be used locally. Sometimes it is ju
 michiel@mitulo:(pomst)(main,80)~/npo/media/main/media-server$ ~/github/npo-poms/kaniko/kaniko.sh
 2 docker build setup
 38 defining os_app_name
-60 defining get_artifact_versions
+60 defining get_docker_image_name
 kaniko build setup
 Defining function setup_kaniko
 Defining function kaniko_execute

scripts/dockerfile-functions.sh

@@ -37,7 +37,7 @@ os_app_name() {
   echo $appname
 }
 
-echo "defining get_artifact_versions"
+echo "defining get_docker_image_name"
 
 # exports PROJECT_VERSION, IMAGE_TAG, IMAGE, IMAGE_NAME
 # $1: directory containing the docker file
@@ -68,4 +68,8 @@ get_docker_image_name() {
   echo "Using image artifact: \"$IMAGE\" (tag: \"$IMAGE_TAG\", full: \"$FULL_IMAGE_NAME\")"
 }
 
+#deprecated
+get_artifact_versions() {
+  get_docker_image_name "$@"
+}
 

scripts/kaniko-functions.sh

@@ -59,7 +59,7 @@ run_kaniko_all() {
   store_variables
 }
 
-#  Stores relevant variables determined by get_artifact_versions in job.env
+#  Stores relevant variables determined by get_docker_image_name in job.env
 #  I'm not sure this is very useful. You can just as wel call get_articaft_versions again in the next job
 #  which will have the same effect, but I think this is robust, because no need for fiddling with 'need=<previous job>',
 #  which is confusing and error-prone.
@@ -109,7 +109,7 @@ kaniko_execute() {
 
   if [ -z "$IMAGE" ] ; then
       echo "Missing IMAGE variable. Trying to find now by calling get_actifact_versions"
-      get_artifact_versions $dir $version
+      get_docker_image_name $dir $version
   fi
   image="$IMAGE"
   if [ -z "$image" ] ; then