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
..
Dockerfile	titan: move from debian-stetch-titan to debian-bullseye-titan	2021-12-16 11:40:17 +01:00
Makefile	ttcn3-stp/Makefile: Drop defaulting to branch laforge/stp	2019-11-12 13:10:38 +01:00
STP_Tests.cfg	ttcn3-stp-test: do not set mp_osmo_stp_newer_than_1_4_0	2021-11-18 22:05:42 +03:00
jenkins.sh	ttcn3: write Osmocom repository to configs	2021-11-26 18:12:50 +01:00
osmo-stp.cfg	ttcn3-stp: Configure M3UA setup to use IPv6 together with IPv4	2020-08-27 10:47:28 +00:00