Started by an SCM change3097ac0902cd740139b0d1cfdbd90179de7379d28837ac0902cd740139b0d1cfdbd90179de7379d2883refs/remotes/origin/osmith/wip-dahdi7ac0902cd740139b0d1cfdbd90179de7379d28837ac0902cd740139b0d1cfdbd90179de7379d2883refs/remotes/origin/osmith/wip-dahdi3500cc339320da7669a00ae8633bfc9be3c354ee9370cc339320da7669a00ae8633bfc9be3c354ee937refs/remotes/origin/master0cc339320da7669a00ae8633bfc9be3c354ee9370cc339320da7669a00ae8633bfc9be3c354ee937refs/remotes/origin/master0cc339320da7669a00ae8633bfc9be3c354ee9370cc339320da7669a00ae8633bfc9be3c354ee937refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#350624255update-osmo-ci-on-slaves-dp #350350falsefalse350744889SUCCESS1652458866234https://jenkins.osmocom.org/jenkins/view/update-jobs/job/update-osmo-ci-on-slaves-dp/350/build2-deb9build-ansible- osmocom-bb-host-master/Dockerfile0cc339320da7669a00ae8633bfc9be3c354ee9371652433100000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deosmocom-bb-host-master: modernize
Do not set up the Osmocom repository inside osmocom-bb-host-master, it
is done in debian-bullseye-build. Without this patch, we actually
installed the debian 9 version of libosmocore-dev in the debian 11
container.
This is part 1/2 of fixing TTCN3-centos-bts-test, which has been failing
since OSMOCOM_REPO_MIRROR was changed in osmo-ci.git. Part 2 is in
osmo-ci I8201f34a0f9747eea78c358a626cc3981d7407c4.
Change-Id: I78e0445a1b82e5cd72ecaa86e8fe25516b19f485
2022-05-13 11:11:40 +02000cc339320da7669a00ae8633bfc9be3c354ee937osmocom-bb-host-master: modernizeeditosmocom-bb-host-master/Dockerfile
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith