Buildman build tool
Buildman builds U-Boot, for many boards and many commits at once, to check that a patch series has not broken anything. It:
builds each commit of a branch for any set of boards, in parallel, making full use of multi-processor machines;
summarises the results, so that new errors, warnings or image-size changes can be pinned to the commit and board which caused them;
fetches the cross-compilers it needs and works out which to use for each board;
can share builds across several machines over SSH;
adjusts board configurations on the fly for build experiments.
Installation
Install the latest release from PyPI:
pip install buildman
The buildman command is then on your path.
Quick start
From a U-Boot source tree, fetch a toolchain and build a board:
buildman --fetch-arch arm buildman -k rpi_2 ls ../current/rpi_2
Build every commit of the current branch for all ARM boards, then show a summary of the results:
buildman -b <branch> arm buildman -b <branch> -s arm
See buildman -H for the complete manual, or the documentation linked below.
Documentation
Full documentation is hosted on Read the Docs:
Development
Run the test suite from a checkout:
pip install -r requirements.txt pip install -e .[test] buildman -t
A few tests run U-Boot’s real Kconfig tools. Set UBOOT_SRC to a U-Boot source tree to include them; otherwise they are skipped. buildman --coverage checks that the tests cover all of the code.
The parts of patman which buildman uses and U-Boot’s qconfig tool are vendored from the U-Boot tree and u_boot_pylib is installed from PyPI as u-boot-pylib, so no surrounding U-Boot source is needed to run the tests.
Metadata
Release files for buildman 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| buildman-0.4.0.tar.gz | 350.3 kB | With provenance | Details for buildman-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| buildman-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for buildman-0.4.0-py3-none-any.whl |
Total release size: 720.5 kB
Release files / buildman-0.4.0.tar.gz
| Download URL | buildman-0.4.0.tar.gz |
|---|---|
| Size | 350.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e6b989e1df7e58b82a8d983503884d6fd5b8669643253bc3968fb2184c1cefc
|
|
BLAKE2b-256 checksum How to use checksums |
cef9269ce3a6006576367ea389087caff4aa2e3d30dba00ef21e6f289b62b571
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.
Transparency logRelease files / buildman-0.4.0-py3-none-any.whl
| Download URL | buildman-0.4.0-py3-none-any.whl |
|---|---|
| Size | 370.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82bdbac2a994b84a1c0f2a93945d907e20885bd8d27760721a4a4ca6102b1082
|
|
BLAKE2b-256 checksum How to use checksums |
7e66b3bc55dca9b90e64492e11e7444e6e976428f78f614b0f7dc796bb8bf330
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.
Transparency logSecurity for buildman 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for buildman-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.