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/registry-trigger-osmo-ttcn3-hacks
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/osmo-ttcn3-hacks'>https://gerrit.osmocom.org/osmo-ttcn3-hacks</a>
 &gt; git init /home/osmocom-build/jenkins/workspace/registry-trigger-osmo-ttcn3-hacks # timeout=10
Fetching upstream changes from <a href='https://gerrit.osmocom.org/osmo-ttcn3-hacks'>https://gerrit.osmocom.org/osmo-ttcn3-hacks</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/osmo-ttcn3-hacks'>https://gerrit.osmocom.org/osmo-ttcn3-hacks</a> +refs/heads/*:refs/remotes/origin/* # timeout=10
 &gt; git config remote.origin.url <a href='https://gerrit.osmocom.org/osmo-ttcn3-hacks'>https://gerrit.osmocom.org/osmo-ttcn3-hacks</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 c568521460426c78a7cc7f68de38af6dfe2c4921 (refs/remotes/origin/master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f c568521460426c78a7cc7f68de38af6dfe2c4921 # timeout=10
Commit message: "testenv: add proper [testsuite] prepare= support"
 &gt; git rev-list --no-walk c1c05554fddeb3502492b49f361a2dd4a67f3e04 # timeout=10
Triggering a new build of <a href='/jenkins/job/registry-rebuild-upload-titan/' class='jenkins-table__link model-link model-link--float'>registry-rebuild-upload-titan</a>
Finished: SUCCESS