Started by an SCM change
Running as SYSTEM
Building remotely on <a href='/jenkins/computer/build2-deb11build-ansible' class='jenkins-table__link model-link model-link--float'>build2-deb11build-ansible</a> (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 <a href='https://gerrit.osmocom.org/docker-playground'>https://gerrit.osmocom.org/docker-playground</a>
 &gt; git init /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves-dp # timeout=10
Fetching upstream changes from <a href='https://gerrit.osmocom.org/docker-playground'>https://gerrit.osmocom.org/docker-playground</a>
 &gt; git --version # timeout=10
 &gt; git --version # 'git version 2.30.2'
 &gt; git fetch --tags --force --progress -- <a href='https://gerrit.osmocom.org/docker-playground'>https://gerrit.osmocom.org/docker-playground</a> +refs/heads/*:refs/remotes/origin/* # timeout=10
 &gt; git config remote.origin.url <a href='https://gerrit.osmocom.org/docker-playground'>https://gerrit.osmocom.org/docker-playground</a> # timeout=10
 &gt; git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
 &gt; git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision ff0b8c6d94f1eba093bc45fbdfbce88f85dfb8d2 (refs/remotes/origin/master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f ff0b8c6d94f1eba093bc45fbdfbce88f85dfb8d2 # timeout=10
Commit message: "Use 2023q1 osmo-ttcn3-hacks branch for 2023q1 SUTs"
 &gt; git rev-list --no-walk d12a63a3a1f8903aa2dfbbcddefee502a0f90e2b # timeout=10
Triggering a new build of <a href='/jenkins/job/update-osmo-ci-on-slaves/' class='jenkins-table__link model-link model-link--float'>update-osmo-ci-on-slaves</a>
Finished: SUCCESS