Robert Schmidt
6a36db4569
Recent refactoring replaced the CreateWorkspace function call with a dedicated XML step (for clarity, and because it avoids needless recreation of workspaces). In the proxy function, the same CreateWorkspace xml step has been added, cloning the OAI RAN repo, when we actually need the repository for the proxy. Hence, fix this by calling the CreateWorkspace() function manually, but only when necessary, to build the proxy. (It would only be a problem if the pipeline would rebuild the proxy, which did not happen because not much work is happening on the proxy repo). Further, refactoring and simplication of the proxy build function were done: - never tag proxy with develop, that makes no sense - overwrite CreateWorkspace() info after having created and used the workspace (the "if" to build the proxy) - simplify copying of logs - add simple unit test - remove check for ubuntu; the dependcy is "docker". Simplify the code to not obscure with a class variable.
In this directory and subdirectories are various CI code test cases and helper scripts.
Unit test
There are some unit tests. From the parent directory, i.e., ci-scripts/,
start with
python tests/build.py -v
python tests/cmd.py -v
python tests/deployment.py -v
python tests/iperf-analysis.py -v
python tests/ping-iperf.py -v
It will indicate if all tests passed. tests/deployment.py requires these
images to be present:
oai-ci/oai-nr-ue:develop-12345678oai-ci/oai-gnb:develop-12345678
It will try to download oaisoftwarealliance/oai-{gnb,nr-ue}:develop
automatically and retag the images.
test-runner test
This is not a true test, because the results need to be manually inspected. To run this "test", run
./run.sh
inside the test-runner/ directory (important!).