commit ed6187cb1bf76a35dd9df1d14b22ab1a68cad699
author Fatih Degirmenci <fdegir@gmail.com> Wed May 08 08:56:52 2019 +0200
committer Fatih Degirmenci <fdegir@gmail.com> Wed May 08 08:58:03 2019 +0200
tree c79e57720f840362757b9d6c3bbac852c35eedaf
parent 7946a5c8faf3c0fb9ea5d4ff6944893efb9dbc00

Enable scenario input for engine verify jobs

There will be cases where we need to specify the scenario to
verify the engine with. Most obvious example to this is while
adding newly implemented scenarios into sdf.yml.

Change-Id: Ia60ac75a9f65f9c29efd9804095f15e2338f9be9

jjb/cloud-infra/cloud-infra-deploy.sh

diff --git a/jjb/cloud-infra/cloud-infra-deploy.sh b/jjb/cloud-infra/cloud-infra-deploy.sh
index 51ae5a3..1a3ebdd 100644
--- a/jjb/cloud-infra/cloud-infra-deploy.sh
+++ b/jjb/cloud-infra/cloud-infra-deploy.sh
@@ -47,6 +47,6 @@
 
 # execute cloud engine deploy.sh script
 cd $WORKSPACE
-./engine/deploy.sh -d kubespray -s $DEPLOY_SCENARIO -p $PDF -i $IDF -c
+./engine/deploy.sh -d $INSTALLER_TYPE -s $DEPLOY_SCENARIO -p $PDF -i $IDF -c
 
 # vim: set ts=2 sw=2 expandtab: