Since osmo-gsm-tester.git Change-Id Ieca65b71b543c44cfcec8e83efd0fe053c432e55,
the -c parameter holds the config file and not the directory where it is contained.
Change-Id: I5aa0507d0e82616ee3cca74573fea6bdb7459b53
As of osmo-gsm-tester.git Change-Id
I7eb69f870d0dcb5906d45ae067d6bed1aabf5862, the enviornment variable
OSMO_GSM_TESTER_CONF is deprecated in favour of already existing -c cmd
line argument. Let's use it while still providing the docker setup with
a way (using same env var name) to modify where the conf dir is to be
found inside the docker container (for instance, to provide an external
conf dir).
Change-Id: I54ea9dc4d0bb205debf312f5a37053bc60cfcdb7
Some days ago the Dockerfile was changed to pull from
debian-stretch-jenkins instead of debian-stretch-build, since the first
one has extra runtime dependencies required by osmo-gsm-tester.
However, the jenkins script is still requiring the old dependency. Let's
update it accordingly.
Change-Id: If33aab60e04da7beb4cd0715d5cb3145c001823a
This way one can quickly see if osmo-gsm-tester run fine or an issue
ocurred and logs need to be checked.
Change-Id: I0b267889f403fc1505f9dd859568bc15a120dd81
It's set to /tmp/trial by default for convenience, since it's a
temporary directory and easy to remember and to access. Still, let's
give the opportunity to change it (if user wants it to be stored in
persistent data or if has low amounts of non-persistent memory).
Change-Id: I2a7ea361c6156c97bd8d2d94cf1b6856344d4d9f
osmo-gsm-tester.git/contrib/jenkins-build-srslte.sh cannot be used
because there's a need to split the fetch step from the build step.
That's because we want to fetch in the host (in order to use host's user
ssh key for potential private repos) while still building inside the
docker container, where we have all the dependencies (and where the
binaries are going to be run afterwards by osmo-gsm-tester).
During the changes above it was also noticed that /tmp/trial on the host
got its UID+GID changed (because we switch user inside the container to
downscale privileges). Fix it by chown'ing the directory back to the
host user's UID+GID.
Change-Id: Ia0db8fba840392a0b7883cfc15e45c2e80407a16
After this patch, one can run osmo-gsm-tester with specific parameters
(debug level, suite and tests to run, etc.) by using
OSMO_GSM_TESTER_OPTS variable:
OSMO_GSM_TESTER_OPTS="-s 4g -t ping -l error" ./jenkins.sh
Change-Id: I2e8ff51a3152125148c6a117a987e8c11a576e1e
* Fix wrong KI.
* Add an extra IP address to slave so that ENB and EPC can be run on
different IP addresses and their GTP ports don't collide.
* Add required rf parameters to resources.conf
Change-Id: I0198bc99f75e9567ee717aa79e434ec28705fac9
This set up allows running a typical osmo-gsm-tester set up with a main
unit (ogt-master) attached to one (or more) slaves where resources are
located and processes are run.
As an example, current config allows running an iperf3 test over an srsLTE
stack using the ZeroMQ backend.
Change-Id: Iac7c0b613048ce332642d3957c55cc7c53b56d42