Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-build-scripts / 927ded2fe2a63bf639d00522ce67fe2d2be5e862
commit927ded2fe2a63bf639d00522ce67fe2d2be5e862[log] [tgz]
authorHariharan Rangasamy <hariharanr@ami.com>Mon Sep 29 15:25:12 2025 +0530
committerHariharan Rangasamy <hariharanr@ami.com>Mon Sep 29 15:56:39 2025 +0530
tree6a18f63bde86781224bc01801cd0127f86e4ad12
parentc5f92c9f46cc6906a935ff67bc92093d6aa6be3d [diff]
build-setup.sh: fix bitbake warnings

Resolved the warning messages encountered during the docker build

WARNING: local.conf:263 has a lack of whitespace around the
assignment: 'DL_DIR="/data0/jenkins/bitbake_downloads"'

WARNING: local.conf:264 has a lack of whitespace around the
assignment: 'SSTATE_DIR="/data0/jenkins/bitbake_sharedstatecache"'

WARNING: local.conf:267 has a lack of whitespace around
the assignment: 'TMPDIR="/data0/jenkins/workspace/latest-master/
label/docker-builder/target/bletchley/build"'

Change-Id: I1596bc0251f3d5b06c24069377313320c973eb7b
Signed-off-by: Hariharan Rangasamy <hariharanr@ami.com>
1 file changed
tree: 6a18f63bde86781224bc01801cd0127f86e4ad12
  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.