Do not brush over VOL_BASE_DIR with a new temp dir, since jenkins-common.sh has
already figured out where these should run.
Should fix jenkins job build failures for mgw and ggsn, after the merge of
I8cf6014725ae8ba602be5f3ec31dfb8e49ff993e.
Change-Id: Iee034df93bf8e8b995262749cf4654886032af2b
On jenkins, place all logs and manage docker volumes in the workspace instead
of a /tmp/* dir. Use $WORKSPACE/logs as docker volume base to begin with, thus
there needs to be no copy from /tmp to $WORKSPACE/logs.
On non-jenkins runs, place all in a /tmp/* dir still, but also skip copying of
the logs: just have a /tmp/logs symlink to the last tmpdir.
Change-Id: I8cf6014725ae8ba602be5f3ec31dfb8e49ff993e
In Change-Id: I1dc299407c61b1c865035add44067b8ab89001b3
a VTY interface was added to osmo-ttcn3-hacks.git, but
it was missed to update the config file here for the dockerized
execution, rendering us with broken test builds ever since.
Change-Id: I9539f7a28cf9214bd73ac9f80d22c71041c47adb
Related: OS#2519
The openid support doesn't allow to add custom providers but we like the
convenience of a single click. Take the official docker image and patch
the HTML template. It seems to have changed little over the time, and it
might continue like that...
I have filed https://bugs.chromium.org/p/gerrit/issues/detail?id=8828 so
that we can drop this hack in the future...
Change-Id: I713948fbb93355c2e33e3b92969e2389cb88c938
To remove code dup and prepare a change to where logs are written, add
collect_logs() to jenkins_common.sh and call that from each jenkins.sh after
the tests are done.
The 'rm -rf' is already done before a test starts. No need to do that again
after each test.
Change-Id: I5d8472ec36b07c828685b1bd7718e31392d168a3
After merging Change-Id: Ie844c4de62e0ef5d5c4c366185968211a7f6d676
in osmo-ttcn3-hacks, the module parameters for BSSAP configuration
require one extra argument.
Change-Id: I2a0011bc6f7bdf013005d1ea36da591673344eed
Related: OS#2544
This is no longer needed as the fix for https://osmocom.org/issues/2718
has been merged to master of osmo-ttcn3-hacks
Change-Id: Ia0c1c134405fdbce1c65059d705827f1a643e774
Related: OS#2718
Te make scripts will generate docker images like
"$username/foobar-test". When depending on an previous image,
the $username must match or the build will about with image not found.
Change-Id: Ied42c3e1de9a2ffaca22ba4cd02e6a398e48e97d
All three BTS are configured for ARFCN 871 and BSIC 63, which causes trouble
for handover tests. Set BSICs to 10, 11 and 12 (not 0,1,2 to mark the
distinction from the cell_identity).
It wasn't a problem so far since we cheated by passing the BTS target number
from VTY. But as soon as we will start identifying handover target cells by
ARFCN+BSIC exclusively, TC_ho_int would fall on its face without this patch.
See also: osmo-ttcn3-hacks I2ea8889ea40953f5a23eab40db52585556a410bc
Change-Id: I29a117aa54aa06ca49646f25a08af8521832fd8d
The 'laforge/trx' branch of OsmocomBB was used to make basic
TTCN3 tests, such as the 'max_ta', work ASAP. Now all required
changes and some bug fixes have been merged to the 'master'.
Change-Id: I4c3012c4ad24dfebea61e14038bea86d4f56832d
This is required by later versions of the osmo-ttcn3-hacks BTS
test suite after Change-Id I2a42531dc5555ab4772d538fda462343605b8feb
Change-Id: I229000ce7609845fdf24cafe1f5ec2bfa3f507e8
$(PWD) reflects the dir of 'make' invocation, $(CURDIR) the dir stepped into.
So obtain the current dir from $(CURDIR) instead of $(PWD).
So far, when doing 'make -C osmo-foo-maser', the image's name would be derived
from the root dir's basename and all images were tagged as 'docker-playground'.
With this fix, 'make -C' from anywhere still tags with the proper name.
Change-Id: I1dd0fd1ad89fdee18fdbea851ccc831ad60aeccf
osmo-ttcn3-hacks adds configuration of the CTRL interface in
I502b4891e6720ae2fb251c03542f707880a6f728. We need proper IP addresses here for
the f_ipa_ctrl_start() to work.
WARNING: This commit has to be merged "at the same time" as
I502b4891e6720ae2fb251c03542f707880a6f728 or the jenkins ttcn3-bts-tests will
fail.
a) if we want to set a modulepar mp_ctrl_ip here, it needs to be added to
osmo-ttcn3-hacks.
b) if we have the f_ipa_ctrl_start() in osmo-ttcn3-hacks, we need to configure
the proper IP and bind interface here, or all tests will fail because
f_ipa_ctrl_start() cannot connect.
Change-Id: I1ec86b157ebd46bf622a0ca51eba225f15c99fbb
the routink key for virt-bsc0-0 and virt-bsc1-0 is the same
(0), virt-bsc0-0 and virt-bsc1-0 should use different routing
keys.
- Keep the routing key of virt-bsc1-0 and assign routing key 1
to virt-bsc1-0
Change-Id: I1380ba389dc777cdac84677588b85759cad4bc14
In osmo-ttcn3-hacks Change-Id I52a4c8118828c1605cf672889982f987568ad17d
we introduced changes to the BSSAP_Adapter, but the config file for
the BSC hasn't been updated accordingly here.
Change-Id: I7cfc6414c1a783bab54f0d82589de82af4764daa
In Change-Id: Ie7780750f7032453951f6849ecee6ab7cc34e8c2 we not only
introduced a MSC_Tests.default with syntax errors, but also a
osmo-stp.cfg with syntax errors :((
Change-Id: If7a7ff3d7ddb255654d14fe17033390214fe5341
The MSC_Tests.ttcn testsuite is now able to present multiple BSC
to the MSC (IUT). This change requires the configuration files
of osmo-stp and of the testsuite to be changed.
- update MSC_Tests.cfg to present up to two BSCs to the MSC
- update osmo-stp.cfg to support the additional connection
from the testsuite
Change-Id: Ie7780750f7032453951f6849ecee6ab7cc34e8c2
Depends: osmo-ttcn3-hacks I52a4c8118828c1605cf672889982f987568ad17d
Related: OS#1609
This uses the debian-nginx container "ankitrgadiya/cgit:debian-nginx"
and adds pygments for syntax highlighting, as well as the osmocom
commit filter for linking to gerrit change-ids as well as
redmine issues
Change-Id: Iec75769a972950ed9df95d5b36aa930daad1565a
The configuration of osmo-bsc currently only supports halfrate
traffic channels. In order to test assignments which contain
half rate codecs we also have to have halfrate channels available.
Change-Id: Ibcce03ab0c98545a1f316d88e1f3dd75e2ff65e1
Related: OS#3100
Related: OS#3095
Allow the osmo-bsc-main docker container to reach the virtual MGW set up by the
ttcn3-bsc-tests.
The module parameter mp_test_ip sets the IP address at which the virtual
services are set up to listen for connections -- currently actually only the
virtual MGW. Set this to 172.18.2.203 instead of using the default 127.0.0.1.
This fixes the second half of the disconnect between BSC and virtual MGW in
this docker setup. The first half is Ib53f000ec7e717b14a3e5df6e803d3d0950b937f
Change-Id: I3038481ed0bba1084b63dc6a6d2ff6e970100890
The osmo-bsc-main docker container is run in a separate docker container and
cannot reach the virtual MGW set up by the ttcn3-bsc-tests.
From ttcn3-bsc-tests/jenkins.sh it is clear that the tests are run at IP
172.18.2.203. Add this as the 'mgw remote-ip' setting in
ttcn3-bsc-tests/osmo-bsc.cfg.
This fixes the first half of the disconnect between BSC and virtual MGW in this
docker setup. The second half is I3038481ed0bba1084b63dc6a6d2ff6e970100890.
Change-Id: Ib53f000ec7e717b14a3e5df6e803d3d0950b937f
In the past, MM INFO transmission was broken, so the tests were
written without expecting it. Now, the bug in osmo-msc has been
fixed.
With the config file enabling it, and the tests not expecting MM INFO,
a lot of them failed. Let's disable MM INFO for now until the tests
can deal with it
We recently introduced verification of the MCC/MNC, and the osmo-msc.cfg
MCC/MNC settings mis-matched those of MSC_Tests.ttcn resulting in lots
of test failures.
Debian 9.0 ships with titan 6.1.0 which for some unknown reasons
causes segfaults in the C++ part when parsing CTRL messages and
according to TITAN project is not supported anymore anyway.
So let's use a 6.3.x build, or whatever is the highest version in
the network:osmocom:latest feed instead.
In osmo-ttcn3-hacks, we have removed the *.control from the *.default
files, so let's add it here in the config files. You can now change
the tests to be executed by simply editing the config here.
Harald Welte
Neels Hofmeyr
Philipp Maier