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	sysinfo: add missing .release file	2017-08-20 23:41:55 +02: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
Test.cfg	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
jenkins.sh	*/jenkins.sh: set -e after setting clean up trap	2021-02-26 09:32:34 +01:00