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 1a47384d81869ab1b82b34f7d1cca90d83e0e1c9 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 1a47384d81869ab1b82b34f7d1cca90d83e0e1c9 # timeout=10 Commit message: "redmine: fix auto-scan of repositories" > git rev-list --no-walk 522783497431f825cf85fdcf21c202d088458a1c # timeout=10 Triggering a new build of update-osmo-ci-on-slaves Finished: SUCCESS