| commit | 037f933db93a5d8400266296704bd2eac6d69d4d | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Aug 18 15:52:08 2025 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Aug 27 14:47:04 2025 +0000 |
| tree | e05d6cfeaf2ba16f2ed40851d135477401d7e122 | |
| parent | 82425eca57edcd053140dd323577697df7996643 [diff] |
config-clang-tidy: support dropping config options The latest docs .clang-tidy reference dropped some config options, so add support for that to the tool. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I4b9c33f9d01697d06574f931aa2c8a782cafc262
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.