Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-build-scripts / 3dc37e6ec0d0ddd68dc2a2287b88357fa3686cc6
commit3dc37e6ec0d0ddd68dc2a2287b88357fa3686cc6[log] [tgz]
authorRatan Gupta <ratankgupta31@gmail.com>Thu Jul 17 16:47:13 2025 +0530
committerRatan Gupta <ratankgupta31@gmail.com>Tue Jul 29 15:06:48 2025 +0530
tree780667d0df1795f0e303a0062b2fdda86c1a82ce
parent8eaac19744415ab0695a0bcdd16dbb88c0fe7746 [diff]
Add DMTF/libspdm v3.7.0 to docker unit test image

Add libspdm library to the docker build environment
to support SPDM.
The library is built with OpenSSL crypto backend
and configured for shared library output.

Tested:
- Verified that local CI passes without errors.
- Confirmed all SPDM libraries and associated header
  files are correctly built and included.

Change-Id: I04c97ae616ada2bc955ac1353ce743dd8ea3ba8a
Signed-off-by: Ratan Gupta <ratankgupta31@gmail.com>
1 file changed
tree: 780667d0df1795f0e303a0062b2fdda86c1a82ce
  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.