docker-playground/ttcn3-msc-test
Harald Welte 0f74af6083 titan: move from debian-stetch-titan to debian-bullseye-titan
So far we were executing all our TTCN-3  tests from a container
image with Debian stretch (9) plus a custom more recent eclipse-titan
package from the osmocom feed.

Let's update the container base OS from stretch (9) to bullseye (11)
while using the same packaged eclipse-titan version (8.0.0) for running
the tests.  So this should be a low-risk change, as titan runtime
remains identical.

I've executed all test suites locally and couldn't see any regressions.

Related: OS#4969
Change-Id: Ib3bdfa3bec8f8ef42c55ca61cdee8fbca923874f
2021-12-16 11:40:17 +01:00
..
.release Add ttcn3-msc-test container with OsmoMSC test suite 2018-01-27 20:25:10 +01:00
Dockerfile titan: move from debian-stetch-titan to debian-bullseye-titan 2021-12-16 11:40:17 +01:00
MSC_Tests.cfg ttcn3-msc: Drop uneeded module params 2021-02-26 13:35:03 +01:00
Makefile migrate ttcn3-msc-test from 172.18.1.0/24 to 172.18.20.0/24 2020-08-14 08:03:41 +02:00
jenkins.sh ttcn3-{bts,bsc,msc,hlr}-test: set OSMO_SUT_{HOST,PORT} 2021-12-01 13:48:50 +00:00
osmo-msc.cfg ttcn3-msc-test/osmo-msc.cfg: disable encryption for UTRAN 2021-12-02 23:57:37 +03:00
osmo-stp.cfg remove deprecated 'logging level all everything' from configs 2021-04-25 13:11:03 +02:00