Started by an SCM change
Running as SYSTEM
Building remotely on <a href='/jenkins/computer/gtp0-deb9build' class='jenkins-table__link model-link model-link--float'>gtp0-deb9build</a> (ttcn3 osmocom-gerrit-debian9 osmocom-master-debian9) 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
 &gt; 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
 &gt; git --version # timeout=10
 &gt; git --version # 'git version 2.11.0'
 &gt; git fetch --tags --progress -- git://git.osmocom.org/docker-playground +refs/heads/*:refs/remotes/origin/* # timeout=10
 &gt; git config remote.origin.url git://git.osmocom.org/docker-playground # 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 854203000876bffb68238d4a42ca46bbcfcd2bb2 (refs/remotes/origin/master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f 854203000876bffb68238d4a42ca46bbcfcd2bb2 # timeout=10
Commit message: "common/Release.key: update"
 &gt; git rev-list --no-walk c6094726aeddeb101a64fd91cc902fb1badeba07 # 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