Move CSIT to integration/csit repo

To facilite branching of CSIT tests, all CSIT test
code and scripts are relocated to the integration/csit
repo.

Change-Id: I6777cd414e43dbf2bfa6215f7e50849e1a6a2e59
Issue-ID: INT-671
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>

1 files changed, 0 insertions, 177 deletions

diff --git a/test/csit/run-csit.sh b/test/csit/run-csit.sh
deleted file mode 100755
index 40cd9ee6d..000000000
--- a/test/csit/run-csit.sh
+++ /dev/null
@@ -1,177 +0,0 @@
-#!/bin/bash
-#
-# Copyright 2016-2017 Huawei Technologies Co., Ltd.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# $1 project/functionality
-# $2 robot options
-# $3 ci-management repo location
-
-
-function docker_stats(){
-    #General memory details
-    echo "> top -bn1 | head -3"
-    top -bn1 | head -3
-    echo
-
-    echo "> free -h"
-    free -h
-    echo
-
-    #Memory details per Docker
-    echo "> docker ps"
-    docker ps
-    echo
-
-    echo "> docker stats --no-stream"
-    docker stats --no-stream
-    echo
-}
-
-if [ $# -eq 0 ]
-then
-    echo 
-    echo "Usage: $0 plans/<project>/<functionality> [<robot-options>] [<ci-management-dir>]"
-    echo
-    echo "    <project>, <functionality>, <robot-options>:  "
-    echo "        The same values as for the '{project}-csit-{functionality}' JJB job template."
-    echo
-    echo "    <ci-management-dir>: "
-    echo "        Path to the ci-management repo checked out locally.  It not specified, "
-    echo "        assumed to be adjacent to the integration repo directory."
-    echo
-    exit 1
-fi
-
-if [ -z "$WORKSPACE" ]; then
-    export WORKSPACE=`git rev-parse --show-toplevel`
-fi
-rm -rf $WORKSPACE/archives
-mkdir -p $WORKSPACE/archives
-
-if [ -f ${WORKSPACE}/test/csit/${1}/testplan.txt ]; then
-    export TESTPLAN="${1}"
-else
-    echo "testplan not found: ${WORKSPACE}/test/csit/${TESTPLAN}/testplan.txt"
-    exit 2
-fi
-
-
-export TESTOPTIONS="${2}"
-
-if [ -z "$3" ]; then
-    CI=${WORKSPACE}/../ci-management
-else
-    CI=${3}
-fi
-
-
-
-
-TESTPLANDIR=${WORKSPACE}/test/csit/${TESTPLAN}
-
-# Assume that if ROBOT_VENV is set, we don't need to reinstall robot
-if [ -f ${WORKSPACE}/env.properties ]; then
-    source ${WORKSPACE}/env.properties
-    source ${ROBOT_VENV}/bin/activate
-fi
-if ! type pybot > /dev/null; then
-    rm -f ${WORKSPACE}/env.properties
-    source $CI/jjb/integration/include-raw-integration-install-robotframework.sh
-    source ${WORKSPACE}/env.properties
-    source ${ROBOT_VENV}/bin/activate
-fi
-
-# install required Robot libraries
-pip install robotframework-selenium2library==1.8.0 robotframework-extendedselenium2library==0.9.1
-
-# install eteutils
-mkdir -p ${ROBOT_VENV}/src/onap
-rm -rf ${ROBOT_VENV}/src/onap/testsuite
-git clone https://gerrit.onap.org/r/testsuite/python-testing-utils.git ${ROBOT_VENV}/src/onap/testsuite/python-testing-utils
-pip install --upgrade ${ROBOT_VENV}/src/onap/testsuite/python-testing-utils
-
-pip freeze
-
-# install chrome driver
-google-chrome --version
-if [ ! -x ${ROBOT_VENV}/bin/chromedriver ]; then
-    pushd ${ROBOT_VENV}/bin
-    wget -N http://chromedriver.storage.googleapis.com/2.35/chromedriver_linux64.zip
-    unzip chromedriver_linux64.zip
-    chmod +x chromedriver
-    popd
-fi
-
-
-WORKDIR=`mktemp -d --suffix=-robot-workdir`
-cd ${WORKDIR}
-
-
-set +u
-set -x
-
-
-# Add csit scripts to PATH
-export PATH=${PATH}:${WORKSPACE}/test/csit/docker/scripts:${WORKSPACE}/test/csit/scripts:${ROBOT_VENV}/bin
-export SCRIPTS=${WORKSPACE}/test/csit/scripts
-export ROBOT_VARIABLES=
-
-# Sign in to nexus3 docker repo
-docker login -u anonymous -p anonymous nexus3.onap.org:10001
-
-# Run setup script plan if it exists
-cd ${TESTPLANDIR}
-SETUP=${TESTPLANDIR}/setup.sh
-if [ -f ${SETUP} ]; then
-    echo "Running setup script ${SETUP}"
-    source ${SETUP}
-fi
-
-# show memory consumption after all docker instances initialized
-docker_stats | tee $WORKSPACE/archives/_sysinfo-1-after-setup.txt
-
-# Run test plan
-cd $WORKDIR
-echo "Reading the testplan:"
-cat ${TESTPLANDIR}/testplan.txt | egrep -v '(^[[:space:]]*#|^[[:space:]]*$)' | sed "s|^|${WORKSPACE}/test/csit/tests/|" > testplan.txt
-cat testplan.txt
-SUITES=$( xargs -a testplan.txt )
-
-echo ROBOT_VARIABLES=${ROBOT_VARIABLES}
-echo "Starting Robot test suites ${SUITES} ..."
-set +e
-python -m robot.run -N ${TESTPLAN} -v WORKSPACE:/tmp ${ROBOT_VARIABLES} ${TESTOPTIONS} ${SUITES}
-RESULT=$?
-set -e
-echo "RESULT: " $RESULT
-rsync -av $WORKDIR/ $WORKSPACE/archives
-
-# Record list of active docker containers
-docker ps --format "{{.Image}}" > $WORKSPACE/archives/_docker-images.log
-
-# show memory consumption after all docker instances initialized
-docker_stats | tee $WORKSPACE/archives/_sysinfo-2-after-robot.txt
-
-# Run teardown script plan if it exists
-cd ${TESTPLANDIR}
-TEARDOWN=${TESTPLANDIR}/teardown.sh
-if [ -f ${TEARDOWN} ]; then
-    echo "Running teardown script ${TEARDOWN}"
-    source ${TEARDOWN}
-fi
-
-# TODO: do something with the output
-
-exit $RESULT