Started by an SCM change
Running as SYSTEM
Building remotely on build2-deb9build-ansible (ttcn3 osmocom-gerrit-debian9 osmocom-master-debian9 repo-install-test coverity) 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 git://git.osmocom.org/docker-playground
 > git init /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves-dp # timeout=10
Fetching upstream changes from git://git.osmocom.org/docker-playground
 > git --version # timeout=10
 > git --version # 'git version 2.11.0'
 > git fetch --tags --progress -- git://git.osmocom.org/docker-playground +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git://git.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 e2ba58222580309556b18fe079c789504561573d (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e2ba58222580309556b18fe079c789504561573d # timeout=10
Commit message: "ttcn3-pcap-client-test: set vty port to 4227"
 > git rev-list --no-walk 5c3ad38f83e7fc4110f7b42ad05f379a062e4a35 # timeout=10
Triggering a new build of update-osmo-ci-on-slaves
Finished: SUCCESS