Commit Graph

4 Commits (0f74af608365df06f96c30003a00abb8e2d5fc65)

Author SHA1 Message Date
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
Pau Espin b9e45af675 hnodeb: Update Dockerfile, configs with new deps, configs
Pull in libgtp, configure LL socket, etc.

Change-Id: I5b223149cbbea16e4ccd9b3874874c6366fe7969
2021-12-15 14:39:32 +00:00
Oliver Smith 305ce55b74 ttcn3: write Osmocom repository to configs
Write a line like 'Misc_Helpers.mp_osmo_repo := "nightly"' into the
TTCN-3 config file (e.g. BSC_Tests.cfg), before starting the testsuite.
This allows executing different code paths in the tests based on the

Related: OS#5327
Change-Id: Ic06532f7a67e59458652c5cf4c8f6fee8113e703
2021-11-26 18:12:50 +01:00
Pau Espin b7c430dd10 Introduce Docker image for ttcn-hnodeb-test
Change-Id: I191b9a29c75d0a1f0bc38d4e29facfc45826cd31
2021-11-24 22:22:29 +00:00