Started by an SCM change29214221979b429ec4918a1c405effb226e17352cac14221979b429ec4918a1c405effb226e17352cacrefs/remotes/origin/master14221979b429ec4918a1c405effb226e17352cac14221979b429ec4918a1c405effb226e17352cacrefs/remotes/origin/master14221979b429ec4918a1c405effb226e17352cac14221979b429ec4918a1c405effb226e17352cacrefs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#2921292255update-osmo-ci-on-slaves-dp #292292falsefalse292634466SUCCESS1639652169151https://jenkins.osmocom.org/jenkins/view/SDR/job/update-osmo-ci-on-slaves-dp/292/gtp0-deb9build- ttcn3-cbc-test/Dockerfiledebian-stretch-titan/Dockerfilettcn3-stp-test/Dockerfilettcn3-msc-test/Dockerfiledebian-bullseye-titan/pipeworkttcn3-bsc-test-vamos/Dockerfilettcn3-bsc-test/Dockerfilettcn3-sgsn-test/Dockerfilettcn3-sip-test/Dockerfiledebian-bullseye-titan/Dockerfilettcn3-hlr-test/Dockerfilettcn3-hnodeb-test/Dockerfiledebian-stretch-titan/.releasettcn3-pcap-client-test/Dockerfilettcn3-mgw-test/Dockerfilettcn3-ns-test/Dockerfilettcn3-fr-test/Dockerfilettcn3-sccp-test/Dockerfilettcn3-nitb-sysinfo/Dockerfilettcn3-smlc-test/Dockerfiledebian-bullseye-titan/ttcn3-docker-prepare.shdebian-bullseye-titan/Makefilejenkins-common.shdebian-stretch-titan/ttcn3-docker-prepare.shdebian-bullseye-titan/ttcn3-docker-run.shttcn3-gbproxy-test/Dockerfiledebian-stretch-titan/pipeworkdebian-stretch-titan/Makefilettcn3-bscnat-test/Dockerfiledebian-stretch-titan/ttcn3-docker-run.shttcn3-remsim-test/Dockerfilettcn3-bts-test/Dockerfilettcn3-ggsn-test/Dockerfilenplab-m3ua-test/jenkins.shttcn3-pcu-test/Dockerfiledebian-bullseye-titan/.release0f74af608365df06f96c30003a00abb8e2d5fc651639651217000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgtitan: 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 +01000f74af608365df06f96c30003a00abb8e2d5fc65titan: move from debian-stetch-titan to debian-bullseye-titaneditttcn3-smlc-test/Dockerfileeditttcn3-sccp-test/Dockerfiledeletedebian-stretch-titan/.releasedeletedebian-stretch-titan/ttcn3-docker-run.sheditttcn3-mgw-test/Dockerfileeditnplab-m3ua-test/jenkins.sheditttcn3-ggsn-test/Dockerfileeditttcn3-bsc-test/Dockerfileeditttcn3-hnodeb-test/Dockerfiledeletedebian-stretch-titan/Makefileeditttcn3-cbc-test/Dockerfileeditttcn3-nitb-sysinfo/Dockerfileeditttcn3-bscnat-test/Dockerfileadddebian-bullseye-titan/.releaseeditttcn3-fr-test/Dockerfileeditttcn3-pcap-client-test/Dockerfileadddebian-bullseye-titan/Makefileeditttcn3-gbproxy-test/Dockerfileadddebian-bullseye-titan/ttcn3-docker-run.sheditttcn3-sip-test/Dockerfileeditttcn3-msc-test/Dockerfileadddebian-bullseye-titan/ttcn3-docker-prepare.shdeletedebian-stretch-titan/pipeworkeditttcn3-bts-test/Dockerfiledeletedebian-stretch-titan/ttcn3-docker-prepare.sheditttcn3-bsc-test-vamos/Dockerfileeditttcn3-stp-test/Dockerfiledeletedebian-stretch-titan/Dockerfileeditttcn3-sgsn-test/Dockerfileeditttcn3-remsim-test/Dockerfileadddebian-bullseye-titan/Dockerfileeditjenkins-common.shadddebian-bullseye-titan/pipeworkeditttcn3-hlr-test/Dockerfileeditttcn3-pcu-test/Dockerfileeditttcn3-ns-test/Dockerfile
- jenkins-common.shmake/Makefilec3874143c020a982c445c4bd352541823353c7c31639651217000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgSwitch ttcn3-* master tests from Debian stretch to bullseys
So far we were using ancient Debian 9 (stretch) for our IUT
containers. Let's upgrade that to Debian 11 (bullseye).
Related: OS#4969
Change-Id: Ic6bece9cb695e6eccfcb1e83fdbf1048724a3cf9
2021-12-16 11:40:17 +0100c3874143c020a982c445c4bd352541823353c7c3Switch ttcn3-* master tests from Debian stretch to bullseyseditjenkins-common.sheditmake/Makefile
- nplab-sua-test/Dockerfilenplab-m3ua-test/jenkins.shnplab-sua-test/jenkins.shnplab-m3ua-test/Dockerfilesigtran-tests/Dockerfilef0554efa92cfe671b34e047c030bd1d9621af67a1639651217000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgnplab: Switch from stretch to buster
The test suites require guile-2.0 so we have to stay with buster
and cannot upgrade to bullseye (guile-3.0 only).
Related: OS#4969
Change-Id: I30c05efbc6c7a21cad71b207e723ef958f1ac9be
2021-12-16 11:40:17 +0100f0554efa92cfe671b34e047c030bd1d9621af67anplab: Switch from stretch to bustereditsigtran-tests/Dockerfileeditnplab-sua-test/jenkins.sheditnplab-sua-test/Dockerfileeditnplab-m3ua-test/Dockerfileeditnplab-m3ua-test/jenkins.sh
- sctp-test/Dockerfile14221979b429ec4918a1c405effb226e17352cac1639651893000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.desctp-test: Upgrade to bullseye
Change-Id: I681802fd779530878c2d2358ebf90b8e2adb4870
2021-12-16 11:51:33 +010014221979b429ec4918a1c405effb226e17352cacsctp-test: Upgrade to bullseyeeditsctp-test/Dockerfile
githttps://jenkins.osmocom.org/jenkins/user/laforgelaforgehttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith