Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-build-scripts / e6d46024496925c52966753fea1e021bf506040d
commite6d46024496925c52966753fea1e021bf506040d[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Mon Sep 15 08:27:57 2025 -0500
committerAndrew Geissler <geissonator@yahoo.com>Mon Sep 15 17:39:10 2025 +0000
tree777d6bfe4544504c0f292d40d42eba29d1c200d7
parent4ce45656f5894a4ae5c048e0753a04b5ab10cae2 [diff]
build-qemu-robot-docker.sh: update to plucky

The previous version has gone EOL

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