docker-playground/ttcn3-pcu-test
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
..
sns ttcn3-pcu-sns: add vty parameter to allow ttcn3 to connect 2021-04-14 12:42:18 +00:00
.release PCU: Add osmo-pcu-* + ttcn3-pcu-test containers 2019-02-20 21:45:07 +00:00
Dockerfile titan: move from debian-stetch-titan to debian-bullseye-titan 2021-12-16 11:40:17 +01:00
Makefile PCU: Add osmo-pcu-* + ttcn3-pcu-test containers 2019-02-20 21:45:07 +00:00
PCU_Tests.cfg ttcn3-pcu: Update config for latest after new osmo-pcu release 2021-11-16 19:12:27 +01:00
jenkins-sns.sh ttcn3: write Osmocom repository to configs 2021-11-26 18:12:50 +01:00
jenkins.sh ttcn3: write Osmocom repository to configs 2021-11-26 18:12:50 +01:00
osmo-pcu.cfg ttcn3-pcu: Update config for latest after new osmo-pcu release 2021-11-16 19:12:27 +01:00