Since examples/sccp_demo_user (the binary used to test SCCP) is not
installed by libosmo-sccp.git during make install, we need to install it
manually after "make" step, and hence it's only available in
osmo-stp-master, because in osmo-stp-latest we used packaged files.
Related: OS#4343
Depends: osmo-ttcn3-hacks.git Ied9fbfb9bd35a99205ca13db033dd9ea03d51238
Change-Id: I5a7e6ff5f6e5f6e34d6a5ab29bd760a6f9d49c4b
Match username of debian-stretch-jenkins, so we can use the same docker
arguments for both images in gerrit-verifications.yml of osmo-ci.git.
Related: OS#4345
Change-Id: Ia3eaec6090c9652549b2850de74ee21730374bbd
Put Dockerfile_osmocom_jenkins.amd64 ("osmocom:deb9_amd64") from
osmo-ci.git here and give it a more descriptive name.
The image is used to run contrib/jenkins.sh scripts of most Osmocom
projects. Move it to here, so we have all docker images in one place.
In the future, osmo-ci.git will use more images from
docker-playground.git in gerrit verification, such as
debian-buster-erlang.
Related: OS#4345
Change-Id: I125ae8a6bcabbd1f485028c79b0abacda0622c3a
This container is useful for people wanting to have an easy method
to gain a build environment for the simtrace2 firmware + host utilities.
Change-Id: I08b2fc542dd3568d26f199427523cfa81eb26d70
The sitmrace2.git firmware buidl requires this cross-compiler. We
so far didn't build it within this container, but lets make sure
we could, if we'd want.
Change-Id: If335247381aab2621fcbe6e6e596a1416e05fdf4
Recent test aiming at dropping different cfg file for latest also
dropped the cp of the regular cfg file. Let's re-add it.
Fixes: 0f34d37491
Change-Id: Ia79e5b50978ed09ce4d0a5a286770e867657ad3e
The idea for this is to be used in build verification for erlang
projects. We also include C compiler and common utilities for those
projects or upstream dependencies that may require it.
Change-Id: I06c11a188404e183ed04bacf1673ecef2dc9ca47
It was removed since latest osmo-ggsn release is nowadays 1.5.0.
Depends: osmo-ttcn3-hacks.git Ie1c3cde2a01e8ea49aadcb1f7384995cb68039cb
Change-Id: I9ffd7549172055e6180a5c3f167dcc1133648243
Latest tagged release of libosmo-sccp, version 1.2.0, already supports
the regular osmo-stp.cfg file.
Change-Id: Ifb3eb642fa5547d1ce2de81f51f181e226dceed7
It was removed since latest osmo-mgw release is nowadays 1.7.0.
Depends: osmo-ttcn3-hacks.git I537c0f5fd6f9e18e111c773c0e42e5f1120ce2f4
Change-Id: Ia457546431e0c3bb3148f4886644ed3fa2513835
NS tests have been splitted recently into their own module. Make sure we
call tests from the new module.
Depends: osmo-ttcn3-hacks.git If680d1bd7dbfe98829f330c33705e0f13bedf3c7
Change-Id: I3e2ec21c56fbfad5d1af051dcc0d0a9c88d2070a
It was noticed that most of the OML related TTCN-3 test cases do not
pass anymore, while some of them are green for the release builds.
The culprit is I49706926b1e962b18791174627bc3cc0cd0cd9d5, which did
not ensure backwards compatibility with older configuration files.
Let's remove 'ms-power-control dsp' and use the defaults.
Change-Id: I940df510d803d0eaa063dd5145c2f9a4c5d0543f
If directory is not created beforehand by the user, docker (root) will
create the directory before binding it to the container.
Related: OS#4313
Fixes: a66f6ebb23
Change-Id: I3f02faef1aa5846c48a3776191c3862bac913d10
The default filename pattern of the JUnit log plugins of TTCN-3 is
"junit-xml-%u.xml" where %u represents the PID of the process. This
is typically a good idea as the PID doesn't wrap that quickly. However,
if you're executing a new docker container for every test suite run,
then chances are high that two subsequent runs of the test suite
container might end up with the same PID and hence the smae filename.
This results in the output file being overwritten, which is what's
responsible for many missing RemsimServer_Tests results on the
jenkins.osmocom.org test results analyzer.
Change-Id: I9b6d1b5a943eb4e058ad2bf7cf8acee7b70e68b6
Closes: OS#4205
Now that osmo-ttcn3-hacks.git I221675721b65b3ab44179e9657da70ba4004d7de
introduced VTY support for PCU_Tests_RAW, we need to use the correct
addr here.
Change-Id: I6807dafd79e58750ffa953da30eb34671aa25808
osmo-sip-connector master and the ttcn3 tests have moved to protocol version 6.
While the extension is gracefully handled by the ttcn templates to make do with
both protocol versions, the actual protocol version number sent to
osmo-sip-connector breaks the tests if it doesn't match. So that master can
still run v6 yet also pass 'latest', configure v5 when the version is not
'master'.
When 'latest' also moves to v6, we of course can revert this again.
Related: Iaca9ed6611fc5ca8ca749bbbefc31f54bea5e925 (osmo-sip-connector)
Related: I39d55432776926a385e1b85b21bcdea8180a8946 (osmo-ttcn3-hacks)
Change-Id: I2174e90bdea32f06cd3e8298696b93027e7906bc
Since we'll now log the script and its children output to a file, let's
make sure the loop doesn't run countless times upon failing child
process, producing lots of potential undesired output. For instance, if
osmo-bts fails to read vty config and exits immediately.
Change-Id: Icc8cac889d94d4cce7d6365781d5b5364404b5b9
That's the default value for all BTS, so no need to have it there.
Furthermore, forthcoming osmo-bts patches will drop osmo-bts-trx support
for DSP/HW based MS Power control, which means BTS will reject this
setting. Let's drop it now and let osmo-bts binary to select the
preferred one.
Related: OS#1851
Change-Id: I0f69880a5028002a53736653735c11ae3cd53f07
Once osmo-ttcn3-hacks.git branch laforge/stp has been merged (where
STP_Tests devel was done), we can use master like we do for other
suites.
Change-Id: I844ecf8a636ead55b7b406cb97424a4a35a6b674
The configuration file for osmo-bsc contains obsolete config statements,
which cause osmo-bsc to crash. Lets remove those config statements.
Change-Id: Ic91e2ee1e9132886cd02535bc84a568d4c25dbb4
The logging categories cc and mgcp are obsolete for osmo-bsc and will
cause recent versions of osmo-bsc to crash. Lets remove this logging
categories from the config file now.
Change-Id: Idd85318abe3fc982909c11115c886835a3d8cd37
OsmoGGSN is not able to use the tun4 device from the default config in
docker. Since the more strict config checking in [1], it does not just
report a warning, but fails to start:
<0002> ggsn.c:189 APN(internet): Opening TUN device tun4
<0001> tun.c:184 errno=2/No such file or directory open() failed
<0002> ggsn.c:191 APN(internet): Failed to configure tun device
Error occurred during reading the below line:
no shutdown
Failed to open config file: '/etc/osmocom/osmo-ggsn.cfg'
Fix the repo install test jenkins job by not checking osmo-ggsn anymore.
In theory, we could probably create the tun device on the host, and
mount it inside the docker container. But that would require some
additional logic to clean it up properly, and it does not seem worth the
effort right now.
[1] libosmocore Ic9c1b566ec4a459f03e6319cf369691903cf9d00
Change-Id: I15c7a2f38a21cd96c9852ad26f4b4a81798e6593
The logging categories cc and mgcp are obsolete. The tests still contain
logging statements with those categories, which makes osmo-bsc
terminate during startup while parsing the configuration file.
Change-Id: Ifd6bf46b73420c0443f997ea953318710544b751
Currently builds from osmo-ttcn3-hacks.git branch laforge/stp instead of
master, since it's only available in the former branch. Once it gets
merged, we can modify Dockerfile as explained in it.
OS#4220
Change-Id: I635c891f5da7b8c59527abbad14d7377465d1045