Started by an SCM change279ff961f6a9b69ceebb1a14ccd53d36717642a6313ff961f6a9b69ceebb1a14ccd53d36717642a6313refs/remotes/origin/masterff961f6a9b69ceebb1a14ccd53d36717642a6313ff961f6a9b69ceebb1a14ccd53d36717642a6313refs/remotes/origin/masterff961f6a9b69ceebb1a14ccd53d36717642a6313ff961f6a9b69ceebb1a14ccd53d36717642a6313refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#2791212255update-osmo-ci-on-slaves-dp #279279falsefalse279627060SUCCESS1638782769975https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/279/gtp0-deb9buildjenkins-common.shf61d3ad8b5f4ac0512bfca9be81c110fcddd9b391638548980000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejenkins-common.sh: fix redundant titan image build Do not build debian-stretch-titan, when registry.osmocom.org is enabled. The image that would be built at this point is not useful, since other images like ttcn3-msc-test will use the debian-stretch-titan image from the registry instead of the one that was just built locally. Related: OS#5336 Change-Id: I7127e3ebac3a6a985c3ba50ba8c7cb8c5de978d9 2021-12-03 17:29:40 +0100f61d3ad8b5f4ac0512bfca9be81c110fcddd9b39jenkins-common.sh: fix redundant titan image buildeditjenkins-common.shjenkins-common.shff961f6a9b69ceebb1a14ccd53d36717642a63131638549028000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejenkins-common.sh: pull registry.osmocom.org imgs Pull debian-stretch-titan from registry.osmocom.org if the repository is enabled. Otherwise the image gets only pulled the first time, and does not get updated once it becomes outdated. Fixes: OS#5336 Change-Id: I1cf998c21e4ee1f723c3b783703e339328377f3e 2021-12-03 17:30:28 +0100ff961f6a9b69ceebb1a14ccd53d36717642a6313jenkins-common.sh: pull registry.osmocom.org imgseditjenkins-common.shgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith