| commit | 3e9c007ca713ed6fbf084fd4fb44b5b558ea9b98 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Aug 27 10:45:22 2025 -0400 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Aug 27 10:50:12 2025 -0400 |
| tree | 759ccb304a4f6eff47998a02674159b9135eb107 | |
| parent | 037f933db93a5d8400266296704bd2eac6d69d4d [diff] |
build-unit-test-docker: sdbusplus: use pip for install Currently sdbusplus uses a setup.py, which is a deprecated method for installing python packages. If we use `pip` here, we can allow it to detect how sdbusplus specifies its installation directives, which will allow transition from the older setup.py to newer pyproject.toml method. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ie956fc32972f4e0ef225a1f8c04d98642098b6a2
Build script for CI jobs in Jenkins.
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.