Skip to content
Started by user Oliver Smith
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/linux-shallow-clone/workspace
The recommended git tool is: NONE
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://gerrit.osmocom.org/osmo-ci
 > git init /var/jenkins_home/jobs/linux-shallow-clone/workspace # timeout=10
Fetching upstream changes from https://gerrit.osmocom.org/osmo-ci
 > git --version # timeout=10
 > git --version # 'git version 2.47.3'
 > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-ci +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://gerrit.osmocom.org/osmo-ci # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
 > git rev-parse refs/remotes/origin/osmith/wip^{commit} # timeout=10
 > git rev-parse osmith/wip^{commit} # timeout=10
Checking out Revision 1fa75345f7a4318c1a87dc959b9b92d2516ad920 (refs/remotes/origin/osmith/wip)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1fa75345f7a4318c1a87dc959b9b92d2516ad920 # timeout=10
Commit message: "TEMP: test linux-shallow-clone from my branch"
 > git rev-list --no-walk 1fa75345f7a4318c1a87dc959b9b92d2516ad920 # timeout=10
Triggering linux-shallow-clone » build5-deb12build-ansible
Triggering linux-shallow-clone » build4-deb12build-ansible
linux-shallow-clone » build5-deb12build-ansible completed with result SUCCESS
linux-shallow-clone » build4-deb12build-ansible completed with result SUCCESS
Finished: SUCCESS