VCA start_build modified to take into account changes in juju client. OSM installer...

[osm/devops.git] / jenkins / RO / start_build

diff --git a/jenkins/RO/start_build b/jenkins/RO/start_build
index 81b337e..c711cd7 100755 (executable)
--- a/jenkins/RO/start_build
+++ b/jenkins/RO/start_build
@@ -25,45 +25,20 @@ OSM_JENKINS=$(dirname $HERE)
 # SET YOU MDG repository name here
 export OSM_MDG=RO
 OSM_load_config
+OSM_git_checkout "$@"
 
 
-# Here is an example for how to handle an incremental build
-if [ -d $OSM_MDG ]; then
-       INFO "reusing existing workspace"
-       cd $OSM_MDG
-        git checkout master  #to make sure that we are in the right branch before pulling the code
-       git pull
-        # TO DO: probably it makes sense to fetch all branches, but this requires creating the branches locally
-else
-       INFO "cloning MDG $OSM_MDG from $OSM_GIT_URL/$OSM_MDG"
-       git clone $OSM_GIT_URL/$OSM_MDG
-       cd $OSM_MDG
-fi
-
-if [ $# -gt 0 ]; then
-        INFO "Code to compile: gerrit refspec '$1', commit-id: '$2'"
-       git fetch origin $1 || FATAL "git fetch origin '$1' didn't work"
-       git checkout -f $2 || FATAL "git checkout -f '$2' didn't work"
-else
-        INFO "Code to compile: master"
-       git checkout master
-fi
-
 INFO "starting build"
 
 INFO "  cleaning .pyc"
 rm -f *.pyc
 INFO "  installing openmano packages and dependencies from current repo (--noclone)"
-./scripts/install-openmano.sh --develop --noclone -q
+./scripts/install-openmano.sh --noclone -q
 INFO "  compiling *.py"
-python -m py_compile *.py
-RC=$?
-
-if RC; then
-       #basic test HERE
-       #RC=$?
-fi
+python -m py_compile *.py   #&&     #uncomment to concatenate commands
+#basic test HERE            #&&     #uncomment to concatenate commands
 
+RC=$?
 INFO "done, RC=$RC"
 exit $RC