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-sgsn-test	2018-02-18 12:47:16 +01:00
Dockerfile	titan: move from debian-stetch-titan to debian-bullseye-titan	2021-12-16 11:40:17 +01:00
Makefile	Add ttcn3-sgsn-test	2018-02-18 12:47:16 +01:00
SGSN_Tests.cfg	ttcn3-sgsn: Update config to test RIM over GTPCv1	2021-05-18 11:18:00 +02:00
jenkins.sh	ttcn3-{sgsn,ggsn}-test: set OSMO_SUT_{HOST,PORT}	2021-12-14 22:09:29 +03:00
osmo-sgsn.cfg	ttcn3-sgsn: Update config to test RIM over GTPCv1	2021-05-18 11:18:00 +02:00
osmo-stp.cfg	remove deprecated 'logging level all everything' from configs	2021-04-25 13:11:03 +02:00