commit | ea1bfb2725470e87286cb15bd0b84700062f75db | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 23 10:46:34 2025 -0400 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 23 11:24:56 2025 -0400 |
tree | a5d274b6b8078cab6fefcb990d6320f1dd6dd767 | |
parent | 6b14190f001cf140921ede2e3317517b700c794b [diff] |
build-unit-test-docker: update gcc to 15 Update to GCC-15 to match Yocto. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Id971752edf536987ef2239d9d6aa45deb4d8ccc8
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.