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 ggsn-test to ttcn3-ggsn-test to align with other naming	2018-03-28 10:37:48 +00:00
Dockerfile	titan: move from debian-stetch-titan to debian-bullseye-titan	2021-12-16 11:40:17 +01:00
GGSN_Tests.cfg	ttcn3-ggsn-test: Use IPv6 address of the tester as "DNS1"	2020-08-16 14:53:36 +02:00
Makefile	rename ggsn-test to ttcn3-ggsn-test to align with other naming	2018-03-28 10:37:48 +00:00
fragment.config	ttcn3-ggsn-test: add kernel test	2021-02-26 09:32:39 +01:00
initrd-ggsn.sh	ttcn3-ggsn-test: add kernel test	2021-02-26 09:32:39 +01:00
jenkins.sh	ttcn3-{sgsn,ggsn}-test: set OSMO_SUT_{HOST,PORT}	2021-12-14 22:09:29 +03:00
osmo-ggsn-kernel-gtp.cfg	ttcn3-ggsn-test: add kernel test	2021-02-26 09:32:39 +01:00
osmo-ggsn.cfg	ttcn3-ggsn-test: Use IPv6 address of the tester as "DNS1"	2020-08-16 14:53:36 +02:00