Clone this repo:
  1. 1832ffa format-code: Print tool versions and describe version policy by Andrew Jeffery · 12 days ago master
  2. a1cbd40 build-unit-test-docker: force refresh container by Patrick Williams · 12 days ago
  3. 7d27a5b Reapply "format-code: fail on markdownlint warnings" by Patrick Williams · 12 days ago
  4. 6100d0b Revert "format-code: fail on markdownlint warnings" by Andrew Jeffery · 13 days ago
  5. e91217e format-code: fail on markdownlint warnings by Patrick Williams · 3 weeks ago

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.