Started by an SCM change
Running as SYSTEM
Building remotely on build3-deb11build-ansible (ttcn3 qemu 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 b268e133191d780c4e4979cd309938a3d36fae39 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f b268e133191d780c4e4979cd309938a3d36fae39 # timeout=10
Commit message: "debian-bullseye-jenkins: add iproute2"
> git rev-list --no-walk 4275e637398e897edbcad52e4659476fb4b52dd4 # timeout=10
Triggering a new build of update-osmo-ci-on-slaves
Finished: SUCCESS