| commit | c5f92c9f46cc6906a935ff67bc92093d6aa6be3d | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 26 07:58:40 2025 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Sep 26 08:01:23 2025 -0400 |
| tree | 57a1ce13c1979079f7941e854e94d3fa65ae9add | |
| parent | e31ec4e3d4d1f5cd75c697592e315f6eeb577b3b [diff] |
build-unit-test-docker: update-alternatives for clang-apply-replacements Meson expects a `clang-apply-replacements` implementation in order to generate the `clang-tidy-fix` target[1,2]. With clang-21, it seems that this moved to a versioned implementation, so we need to include it in the `update-alternatives` invocation. [1]: https://github.com/mesonbuild/meson/blob/3708730dee5049eca7e497629d25629534ea4964/mesonbuild/backend/ninjabackend.py#L3907 [2]: https://github.com/mesonbuild/meson/blob/3708730dee5049eca7e497629d25629534ea4964/mesonbuild/environment.py#L320 Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I7d3099ac7cd675755131a1385f4ce0fc15dc55f7
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.