Started by an SCM change Running as SYSTEM Building remotely on build2-deb11build-ansible (ttcn3 obs osmocom-gerrit coverity osmocom-master) in workspace /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves-dp The recommended git tool is: NONE No credentials specified Wiping out workspace first. Cloning the remote Git repository Cloning repository https://gerrit.osmocom.org/docker-playground > git init /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves-dp # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/docker-playground > git --version # timeout=10 > git --version # 'git version 2.30.2' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/docker-playground +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://gerrit.osmocom.org/docker-playground # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 Avoid second fetch > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 Checking out Revision ef173eb53492dd1e831a1b736e4431cc23eb662f (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ef173eb53492dd1e831a1b736e4431cc23eb662f # timeout=10 Commit message: "ttcn3-bts-test: abort if missing osmo-config-merge" > git rev-list --no-walk d8c51cce641aa7f00f9bc580d2250a2e6cdd8ede # timeout=10 Triggering a new build of update-osmo-ci-on-slaves Finished: SUCCESS