Started by an SCM change00444054051.0096309630622a749a0b4aefed649d8bc2c5012a8386a4ad838f1a749a0b4aefed649d8bc2c5012a8386a4ad838f1refs/remotes/origin/mastera749a0b4aefed649d8bc2c5012a8386a4ad838f1a749a0b4aefed649d8bc2c5012a8386a4ad838f1refs/remotes/origin/mastera749a0b4aefed649d8bc2c5012a8386a4ad838f1a749a0b4aefed649d8bc2c5012a8386a4ad838f1refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#622405255update-osmo-ci-on-slaves-dp #622622falsefalse6221670376SUCCESS1726042870135https://jenkins.osmocom.org/jenkins/view/SDR/job/update-osmo-ci-on-slaves-dp/622/build2-deb11build-ansibledebian-bookworm-build-arm/Dockerfilea749a0b4aefed649d8bc2c5012a8386a4ad838f11726042724000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dedebian-bookworm-build-arm: FROM: add arm32v7 Use the arm32v7 architecture explicitly, instead of implicitly using the same architecture as the host. That way we can use the arm32v7 image on a raspberry pi 4, even if the host system is 64 bit arm. Using 32 bit arm instead of aarch64 is needed for the osmo-trx jenkins jobs, which test -mfpu=neon and -mfpu=neon-vfpv4 build flags. Related: https://github.com/docker-library/official-images#architectures-other-than-amd64 Change-Id: I93986569a9f492237da28fbc534ac5ccd176f120 2024-09-11 08:18:44 +0000a749a0b4aefed649d8bc2c5012a8386a4ad838f1debian-bookworm-build-arm: FROM: add arm32v7editdebian-bookworm-build-arm/Dockerfilegithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith