Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-build-scripts / 6ac3236f8c94d2e71bad70a9fc1eedc4eb0632df
commit6ac3236f8c94d2e71bad70a9fc1eedc4eb0632df[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Wed Jan 21 07:22:57 2026 -0600
committerAndrew Geissler <geissonator@yahoo.com>Wed Jan 21 13:38:00 2026 +0000
treea857c1a0789f39b3cc9c1fbc0b0f11093cf05879
parent70b1ad9844abdac071bc4f8f6b89dbf318deca77 [diff]
userid-validation: add axiado

CCLA accepted and uploaded to google drive

Change-Id: I3110ad22d845e6ee96d50cede7d44f0ea0022c17
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: a857c1a0789f39b3cc9c1fbc0b0f11093cf05879
  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.