diff options
| author | Harald Welte <laforge@osmocom.org> | 2021-12-15 15:42:17 +0100 |
|---|---|---|
| committer | Harald Welte <laforge@osmocom.org> | 2021-12-16 11:40:17 +0100 |
| commit | 0f74af608365df06f96c30003a00abb8e2d5fc65 (patch) | |
| tree | 14ee00d605bc78fff1371acc6ea8af427ee0cd78 /ttcn3-mgw-test | |
| parent | 6f43284ee541f127a61933f886947bd218208f99 (diff) | |
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
Diffstat (limited to 'ttcn3-mgw-test')
| -rw-r--r-- | ttcn3-mgw-test/Dockerfile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ttcn3-mgw-test/Dockerfile b/ttcn3-mgw-test/Dockerfile index 087dc09..c8eeb2b 100644 --- a/ttcn3-mgw-test/Dockerfile +++ b/ttcn3-mgw-test/Dockerfile @@ -1,6 +1,6 @@ ARG REGISTRY ARG USER -FROM $REGISTRY/$USER/debian-stretch-titan +FROM $REGISTRY/$USER/debian-bullseye-titan ARG OSMO_TTCN3_BRANCH="master" ADD http://git.osmocom.org/osmo-ttcn3-hacks/patch?h=$OSMO_TTCN3_BRANCH /tmp/commit |