Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-build-scripts / e31ec4e3d4d1f5cd75c697592e315f6eeb577b3b
commite31ec4e3d4d1f5cd75c697592e315f6eeb577b3b[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Wed Sep 03 15:30:22 2025 -0400
committerPatrick Williams <patrick@stwcx.xyz>Wed Sep 24 16:37:32 2025 +0000
tree7f8b3113b8d3c56f887a22468d82acb7ddc97b01
parentd200508d73cc3a562a1a3dae4bf25fea877bee01 [diff]
build-unit-test-docker: clang: update to 21

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I795e88ada8e676c242b5a18888ce9c08afdedc93
1 file changed
tree: 7f8b3113b8d3c56f887a22468d82acb7ddc97b01
  1. config/
  2. jenkins/
  3. scripts/
  4. tools/
  5. .markdownlint.yaml ⇨ config/markdownlint.yaml
  6. .prettierrc.yaml ⇨ config/prettierrc.yaml
  7. .gitignore
  8. .shellcheck
  9. build-rootfs-size-docker.sh
  10. build-setup.sh
  11. LICENSE
  12. OWNERS
  13. qemu-build.sh
  14. README.md
  15. run-qemu-robot-test.sh
  16. run-rootfs-size-docker.sh
  17. run-unit-test-docker.sh
README.md

openbmc-build-scripts

Build script for CI jobs in Jenkins.

Linter policy and related build failures

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.