Started by user ha:////4AbNqufz7OTIQEW6Q7FwNEOMohzJqRf7kPfftV6SIJMBAAAAmB+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZe/dLi1CKgGWn5RempAPVfFBHCAAAAlaforge
Rebuilds build #ha:////4KGnfqVQvfTc5fGQRVUkk2SXl67iEcr2hpM6qUaQ8FWTAAAAoR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyWEgZR/az8JH3/4tz85Pxcl/zkYn1DcwNjADdNYyPKAAAA1703
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/OsmocomDocs/workspace
The recommended git tool is: NONE
No credentials specified
 > git rev-parse --resolve-git-dir /var/jenkins_home/jobs/OsmocomDocs/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gitea.osmocom.org/phone-side/osmocom-docs # timeout=10
Fetching upstream changes from https://gitea.osmocom.org/phone-side/osmocom-docs
 > git --version # timeout=10
 > git --version # 'git version 2.39.5'
 > git fetch --tags --force --progress -- https://gitea.osmocom.org/phone-side/osmocom-docs +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 03922c27507e539b67f2b9a40c2eb6423a00da4a (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 03922c27507e539b67f2b9a40c2eb6423a00da4a # timeout=10
Commit message: "misc: Add a top level README to describe the purpose of this repository"
 > git rev-list --no-walk 03922c27507e539b67f2b9a40c2eb6423a00da4a # timeout=10
Triggering ha:////4EK8S+i6BFIEZJamFekgMIgu2DXq1wa7p2W3hdrYkVwuAAAAuR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz1EgZD/az8JH3/4tz85Pxcl/zkYqBxSak5tkmlmTkpRropqUmGhmC2bmJecWZSTqo+AClnJivmAAAAOsmocomDocs » build2-deb11build-ansible
Configuration ha:////4EK8S+i6BFIEZJamFekgMIgu2DXq1wa7p2W3hdrYkVwuAAAAuR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz1EgZD/az8JH3/4tz85Pxcl/zkYqBxSak5tkmlmTkpRropqUmGhmC2bmJecWZSTqo+AClnJivmAAAAOsmocomDocs » build2-deb11build-ansible is still in the queue: Waiting for next available executor on ‘ha:////4ILNfMVtewNwPthsDqhmIW1GKP1oxRYoWvG2XTJPT3XSAAAAsB+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzJEgYN/eT83ILSktQi/aTSzJwUI1Ujl5TUJENDMA/IScwrzkzKSdUHAIrNwPHdAAAAbuild2-deb11build-ansible’
ha:////4EK8S+i6BFIEZJamFekgMIgu2DXq1wa7p2W3hdrYkVwuAAAAuR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz1EgZD/az8JH3/4tz85Pxcl/zkYqBxSak5tkmlmTkpRropqUmGhmC2bmJecWZSTqo+AClnJivmAAAAOsmocomDocs » build2-deb11build-ansible completed with result SUCCESS
Finished: SUCCESS