Fix for Osmocom programs using system's shared libraries, instead of the
ones mounted into /usr/local.
For example, for osmo-bsc the libosmocore installed in the
osmo-bsc-master docker container would be used (installed via apt from
OBS nightly) instead of the version that osmo-dev built from source.
Change-Id: I0dd7fb544ca59cb1df19fc3d73cfd07f3374e123
Add the image suffix to the marker in run_docker() which indicates if
the testsuite docker container was already built (with all its
dependencies), so the script doesn't assume that everything is already
built if using without IMAGE_SUFFIX first and then switching to
IMAGE_SUFFIX=latest.
Add an usage example to README for IMAGE_SUFFIX=latest.
Change-Id: I867740831810324a7f5906a0548f0d04ecb9a0a1
Speed up tests by not running a separate docker instances first that
lists installed packages.
Depends: docker-playground Iaafb81e9ee94850ae3b6318574ad5370d74a2838
Change-Id: I3d9976d07f088e2d106d23259889a4bffe1abbcb
Make logic to install the file simpler while at it, and allow it to
create /usr/local/bin if it doesn't exist (I just had that).
Change-Id: I497b9e8909a419f5b5286fcccce9d8a1ba9d515c
Instead of trying to run everything outside of docker, just build the
docker containers and then mount /usr/local and osmo-ttcn3-hacks from
the host system into the docker containers. This way, we can just use
the same configs as the official jenkins jobs are using, while still
having a short test-cycle once the docker containers are built for the
first time. I've decided to implement this, because it was not feasible
to maintain the separate configs.
Depends: docker-playground I8d1f78aee926f8f6ec0b704e16639bc83f525816
Change-Id: Iecba5391dafc353058d369deb513b156534face1
Build testsuite, SUT and dependencies and run everything with one
command. Example usage:
$ ./ttcn3/ttcn3.sh msc
So far, it works at least with:
hlr, mgw, msc, pcu, pcu-sns, sgsn
Change-Id: I6b4bf2743adeec1a950d5f090a690182b991cf49
Oliver Smith