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
..
fh	*/osmo-bsc.cfg: remove obsolete no-op parameters	2021-03-09 13:50:41 +01:00
oml	bts-oml: Set mp_pcu_socket	2021-06-28 14:25:43 +02:00
virtphy	*/osmo-bts.cfg: remove obsolete 'uplink-power-target'	2021-03-09 11:42:38 +01:00
.release	Add osmo-bts-test + dependencies	2018-03-01 15:19:49 +00:00
BTS_Tests.cfg	ttcn3-bts-test: set bind address for the RTP Emulation	2021-07-17 22:37:24 +06:00
Dockerfile	titan: move from debian-stetch-titan to debian-bullseye-titan	2021-12-16 11:40:17 +01:00
Makefile	Add osmo-bts-test + dependencies	2018-03-01 15:19:49 +00: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	*/osmo-bsc.cfg: remove obsolete no-op parameters	2021-03-09 13:50:41 +01:00
osmo-bts.cfg	ttcn3-bts-test/osmo-bts.cfg: use default {fn,rts}-advance values	2021-12-14 13:01:36 +00:00