commit | c7e719f9b58e2e27a13586b3ef33b14fa5e2941d | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Jul 24 16:51:57 2025 -0400 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Jul 25 10:23:41 2025 -0400 |
tree | 396994a2a802883bba4b36fe5fc5a00b22c4de92 | |
parent | ff8e7a4387af2ab8aec26e51bc3eef3a292bbbb0 [diff] |
build-unit-test-docker: force libgpiod 1.x series Latest ubuntu switched to libgpiod 2.x, which we do not support yet in OpenBMC. Convert from using a deb to manually building the 1.x package. Tested: Ran against entity-manager and confirmed that subproject build was no longer selected. ``` Run-time dependency libgpiodcxx found: YES 1.6.5 ``` Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I556574c3cf728932e90f98286871a365d92c91f9
Build script for CI jobs in Jenkins.
Formatting linters sometimes change stylistic output across releases. Separately, some linters are not version-pinned in the CI container, as pinning would drive either frequent maintenance with upgrades or stagnation of the code-base against older versions.
The combination may result in inconsistent formatting opinions across CI worker nodes[^1].
If you see such behaviour consider changing the thing to force a container refresh.
[^1]: The collection of container builds across all worker nodes may not hold a consistent set of tool versions despite being built from the same specification: The inconsistencies emerge from the cadence of upstream tool package updates beating against the cadence of container rebuilds on the worker nodes.