Started by an SCM change297140a22747274ab381dbf0ea882a9ce5a8a252ef5140a22747274ab381dbf0ea882a9ce5a8a252ef5refs/remotes/origin/master140a22747274ab381dbf0ea882a9ce5a8a252ef5140a22747274ab381dbf0ea882a9ce5a8a252ef5refs/remotes/origin/master140a22747274ab381dbf0ea882a9ce5a8a252ef5140a22747274ab381dbf0ea882a9ce5a8a252ef5refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#2971193255update-osmo-ci-on-slaves-dp #297297falsefalse297639188SUCCESS1640280070149https://jenkins.osmocom.org/jenkins/view/SDR/job/update-osmo-ci-on-slaves-dp/297/gtp0-deb9buildjenkins-common.sh140a22747274ab381dbf0ea882a9ce5a8a252ef51640274731000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejenkins-common.sh: add d9 to upstream_distro func After the default UPSTREAM_DISTRO was changed from debian:stretch to debian:bullseye, the "debian9-repo-install-test" container has gotten built with bullseye instead of stretch. This is the reason for failures of the jenkins job Osmocom-repo-install-debian9 we have seen over the past days. With this patch applied, it runs through again: https://jenkins.osmocom.org/jenkins/job/Osmocom-repo-install-debian9/339/ Change-Id: I98a19184ba936114c03cd5cc4f54a3173cbd9cfe 2021-12-23 16:52:11 +0100140a22747274ab381dbf0ea882a9ce5a8a252ef5jenkins-common.sh: add d9 to upstream_distro funceditjenkins-common.shgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith