With libosmocore commit the SNS configuration requires a ip-sns-bind vty configuration
to define the binds which should be use.
Depends-on: I9ab8092bf286e7d90e92f5702a5404425e959c84 (libosmocore)
Fix error message reported by Pau:
docker: invalid reference format: repository name must be lowercase.
This happens in the "docker run" command after the "Starting container
to merge logs" message, because the arguments to --entrypoint are not in
quotation marks. The command fails.
Logs were merged anyway, because
If03422bb8fb126fe6f204a4f8bc6edf0cbb7f194 had already reverted half the
patch and added the log merging back to the Dockerfile.
This reverts commit 73663b01f2.
Allow jenkins to fetch the image from our private docker registry.
Outside of jenkins, the image is built locally just like before.
Move the shared pipework script to the base image, and call it in
ttcn3-docker-run.sh if WAIT_FOR_NETDEV is set. Use ttcn3-docker-run.sh
as entrypoint in both Dockerfiles and remove the custom entrypoint
scripts (which are the same as ttcn3-docker-run.sh now).
Move the git fetch/checkout code and make call to build the testsuite,
to debian-stretch-titan/ttcn3-docker-prepare.sh. In the next patch, I
will extend the script to update deps right before building too (e.g.
because OSMO_TTCN3_BRANCH changed).
After the initial clone of osmo-ttcn3-hacks and deps, let docker
download deps/Makefile to invalidate the cache if the file changed.
Run "git pull" and "make deps" afterwards, but only if the Makefile is
different. The "if" saves time in the initial build of the image, it
avoids the "git fetch" on every dependency repository during "make deps".
Clone the osmo-ttcn3-hacks and all dependency repositories less often by
moving related commands to the shared debian-stretch-titan image.
Remove the 'git checkout -f -B master origin/master' line, because the
master branch is checked out by default.
While at it, move the shared "git config" commands too, and move them
before cloning the repositories, so they don't run again whenever the
deps change (logic to invalidate the cache if deps change will be added
in the next patch).
Remove leftover from old TTCN-3 build scripts, before refactoring ttcn3
Dockerfiles. This line has already been removed in 357ec806 from 2017 for
In osmo-ttcn3-hacks.git, this is only referenced in the obsolete
bin/install.script (looks like we could remove that, together with the
rest of the bin dir?).
In Osmocom we annotate osmocom issues as OS#1234 and not just as #1234,
in order to distinguish them from redmine or coverity issues.
Related: OS#5005, OS#3291
On our deb10fr VMs we have the modified kernel HDLC module supporting
the frame relay MTU up to 1700 bytes, so let's extend our tests to cover
that. Mainline kernels only support 1500 bytes.
Depends: osmo-ttcn3-hacks.git I8e38ecf6b270c81bd73ee43b1fa0b259a999c14b
FRNET_Tests is not a test suite, but just a stub against which we
execute FR_Tests. Hence, we don't want it to generate a junit-xml,
as that doesn't contain any errors and only upsets our jenkins
test results analyzer, assuming the tests have failed.
Requires: osmo-ttcn3-hacks.git Id296e62fb86731492d42370173a48f217b2fbdc0
Since Id35f40d05f3e081f32fddbf1fa34cb338db452ca, osmo-pcu also
depends on libosmoctrl. Debian based images work just fine,
because they depend on libosmocore-dev, while for CentOS we
need to specify all sub-libraries explicitly.
Change the whole vty configuration for NS to be more flexible
and support more setups. Old configurations are invalid.
For further information see:
Depends-on: Ie9306ab4d4738c2c57a69987086e22771b30657e (osmo-sgsn)
Make debian-repo-install-test simpler before copying it for debian10.
Don't install Release.key, as it is getting downloaded on demand in the
related repo-install-test script since osmo-ci
Starting from build #245  all test cases fail due to DTE:
RAW_NS.ttcnpp:62 Dynamic test case error:
Text encoder: Encoding an unbound integer value.
This happens because fields 'data_weight' and 'signalling_weight'
are both unbound for two additional NS providers. Fix this.
This follows the change implemented in osmo-ttcn3-hacks.git
If0e404bdf2c30a5e18748695608611be83f61109 to use data-only
and signalling-only NS-VCs on the SGSN side
Requires: osmo-ttcn3-hacks.git If0e404bdf2c30a5e18748695608611be83f61109
In upstream I9798e639b4bc8658482945970775b012b5840779 we introduce
two additional fields per NSVC (data_weight, signalling_weight). Make
sure those are specified everywhere.
Requires: osmo-ttcn3-hacks.git I9798e639b4bc8658482945970775b012b5840779
With the change to NS_Provider the configruation has to be extended to also include
the other nsvcs.
osmo-ttcn3-hacks: c316572db111 ("RAW_NS: rework NS connection to use NS_Provider")
PATH isn't overwritten anymore when jenkins runs docker in osmo-ci.git's
master-builds.yml / gerrit-verifications.yml, therefore we can remove
Clone osmo-ci.git, and install all files from scripts/* to
/usr/local/bin. Together with osmo-ci
I45bd7ea56849dab839a98cfd52806f7cd288094e, this will make overwriting
In commit 2279aac6 dumpcap is used to capture pcaps, but dumpcap fails
if the directory isn't writable for everyone.
Commit 62ac27779 only fixed this issue for frame relay, this simply
mirrors the change for ttcn3-gbproxy-test
Related: OS#4518 SYS#5115
In osmo-sgsn Change-Id Id67592aa7712e5e04e7264b2fb8f26d57eb7e69e we
have changed the config file syntax and must adjust here accordingly.
Depends: osmo-sgsn Id67592aa7712e5e04e7264b2fb8f26d57eb7e69e