Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-build-scripts / cc6e4e0b84abb9ca31ce8799c2b29e60e304dddb
commitcc6e4e0b84abb9ca31ce8799c2b29e60e304dddb[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Mon Dec 08 14:19:13 2025 -0500
committerPatrick Williams <patrick@stwcx.xyz>Mon Dec 08 14:19:15 2025 -0500
tree49a6c65bfe17fe02de52c26d88a9818433a8141d
parente6dadf7e39a13db8fe2049850c04036af7a2e63d [diff]
build-seed: add clemente

Clemente is a Meta platform using the GB300 hardware from Nvidia.  It
is similar in design to Catalina (GB200) but the next generation.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4dc014c7346297e10cc6f6cb0ef9862495f26889
1 file changed
tree: 49a6c65bfe17fe02de52c26d88a9818433a8141d
  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.