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
..
sccplite	ttcn3-bsc-test: Leave mp_enable_dyn_sdcch8_test enabled in latest	2021-11-16 19:00:36 +01:00
.release	add ttcn3-bsc-test container with osmo-bsc test suite	2017-12-17 17:21:04 +01:00
BSC_Tests.cfg	ttcn3-bsc-test: Leave mp_enable_dyn_sdcch8_test enabled in latest	2021-11-16 19:00:36 +01:00
Dockerfile	titan: move from debian-stetch-titan to debian-bullseye-titan	2021-12-16 11:40:17 +01:00
Makefile	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
jenkins-sccplite.sh	ttcn3: write Osmocom repository to configs	2021-11-26 18:12:50 +01:00
jenkins.sh	ttcn3-{bts,bsc,msc,hlr}-test: set OSMO_SUT_{HOST,PORT}	2021-12-01 13:48:50 +00:00
osmo-bsc.cfg	Revert "ttcn3-bsc-test: enable A5/4 support in osmo-bsc.cfg"	2021-07-09 15:10:51 +02:00
osmo-stp.cfg	bsc-test: Reduce log verbosity of osmo-stp	2021-12-15 18:05:19 +00:00