Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-build-scripts / 96ce4b451c84cd2c7c972b37a72bec8cd7c256b3
commit96ce4b451c84cd2c7c972b37a72bec8cd7c256b3[log] [tgz]
authorEd Tanous <ed@tanous.net>Fri Jul 25 15:10:49 2025 -0700
committerEd Tanous <ed@tanous.net>Fri Jul 25 15:10:49 2025 -0700
treef798ad4db8a8bf5f03d31356366fe49aa709918c
parentc7e719f9b58e2e27a13586b3ef33b14fa5e2941d [diff]
Set CXXFLAGS for clang

CXXFLAGS is more arguably correct.  Fix it.

Change-Id: I0cd9bacfd4e6453c9e36879581aadde9792e31bd
Signed-off-by: Ed Tanous <etanous@nvidia.com>
1 file changed
tree: f798ad4db8a8bf5f03d31356366fe49aa709918c
  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.