docker-playground/ttcn3-mgw-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 rename mgw-test to ttcn3-mgw-test to align with other containers 2018-03-28 12:27:12 +02:00
Dockerfile titan: move from debian-stetch-titan to debian-bullseye-titan 2021-12-16 11:40:17 +01:00
MGCP_Test.cfg MGCP_Test: set STATSVTY.CTRL_HOSTNAME 2021-08-06 14:11:23 +00:00
Makefile rename mgw-test to ttcn3-mgw-test to align with other containers 2018-03-28 12:27:12 +02:00
jenkins.sh ttcn3: write Osmocom repository to configs 2021-11-26 18:12:50 +01:00
osmo-mgw.cfg osmo-mgw.cfg: configure control interface 2021-08-20 11:14:38 +02:00