Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-build-scripts / 30f8ede9a0235118606cb9ff861ceeab3408800f
commit30f8ede9a0235118606cb9ff861ceeab3408800f[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Tue Jul 08 09:18:25 2025 -0500
committerAndrew Geissler <geissonator@yahoo.com>Tue Jul 08 09:18:25 2025 -0500
treea33de719d26e8201e045c10bc723c86c911c251d
parentd0667786542754f14a04a98eb49bcd8c9f2b6704 [diff]
userid-validation: add qualcomm

CLA update has been processed and there is now an active member in
gerrit so add to approve list

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