Removing juju installation in the jenkins pipeline
With the new way of the juju accces in k8s_08 testsuite,
installing juju in the container is not needed.
k8s_08 testsuite changes: https://osm.etsi.org/gerrit/c/osm/tests/+/11104
Change-Id: I945aa6995241869926c5f76ec9c3eaf960576920
Signed-off-by: aktas <emin.aktas@ulakhaberlesme.com.tr>
(cherry picked from commit 8e0504fac0d2280b41a07f1e4c124c376997c50d)
diff --git a/robot-systest/run_test.sh b/robot-systest/run_test.sh
index 75cd0d4..dd77f8e 100755
--- a/robot-systest/run_test.sh
+++ b/robot-systest/run_test.sh
@@ -150,7 +150,6 @@
-v <path_to_reports>:/reports osmtests \\
-v <path_to_clouds.yaml>:/robot-systest/clouds.yaml \\
-v <path_to_kubeconfig>:/root/.kube/config \\
- -v <path_to_jujudata>:/root/.local/share/juju \\
-o <osmclient_version> \\
-p <package_branch> \\
-t <testing_tags>
@@ -166,8 +165,7 @@
Volumes:
<path_to_reports> [OPTIONAL]: It is the absolute path to reports location in the host
<path_to_clouds.yaml> [OPTIONAL]: It is the absolute path to the clouds.yaml file in the host
- <path_to_kubeconfig> [OPTIONAL]: It is the kubeconfig file to be used for k8s clusters
- <path_to_jujudata> [OPTIONAL]: It is the jujudata file to be used for juju cli"
+ <path_to_kubeconfig> [OPTIONAL]: It is the kubeconfig file to be used for k8s clusters"
exit 0
;;