docker-playground/ttcn3-ns-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
..
fr ttcn3-ns-test-fr: set correct ns configuration to match tests 2021-10-19 18:46:51 +02:00
sgsn-sns ttcn3-ns-test-sgsn-sns: add test run for ns sgsn role with sns 2021-09-06 16:53:38 +02:00
sns ttcn3-ns-test: add second NSVC to allow SNS tests to work 2021-09-06 16:53:38 +02:00
Dockerfile titan: move from debian-stetch-titan to debian-bullseye-titan 2021-12-16 11:40:17 +01:00
Makefile Add ttcn3-ns-test container 2021-03-30 20:32:52 +02:00
NS_Tests.cfg ttcn3-ns-test: add second NSVC to allow TC_tx_blocked_foreign_nsvc to work 2021-09-23 15:48:56 +02:00
jenkins-fr.sh ttcn3: write Osmocom repository to configs 2021-11-26 18:12:50 +01:00
jenkins-sgsn-sns.sh ttcn3: write Osmocom repository to configs 2021-11-26 18:12:50 +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-ns-dummy.cfg ttcn3-ns-test: add second NSVC to allow TC_tx_blocked_foreign_nsvc to work 2021-09-23 15:48:56 +02:00