BuildPilot
What it is not
What it leaves alone.
What it does not do
- Replace your build system. PowerShell, Cargo, npm and the rest stay in charge. Every script stays runnable without BuildPilot.
- Pipelines. No dependency graph, no conditions and no Run All. The only sequence is an operation's own steps.
- Build environments. It uses a Python environment that exists; it never creates, installs into or repairs one.
- Terminals. Output is shown as it arrives; a running script cannot be typed into.
- Touch your scripts. It never writes to, renames or deletes one. Remove takes an operation off the deck along with any icon BuildPilot copied for it and its run times; nothing else.
- Anything but Windows. Windows only, for good.
How it is built
A small tool, held to a large standard.
BuildPilot is written in Rust with a Slint interface. Every number below was measured from the code, not rounded up for the page.
Tests, from pure rules through real processes started and stopped to the keyboard ring driven by real key events.
Of lines and of branches covered in the rules, the use cases and the setup program's policy. The build refuses to run below it.
Lines of requirements, each tied to the test that proves it. Every change of mind is a numbered amendment.
Network request: asking GitHub whether a newer release is out. It names BuildPilot and its version and nothing about you or your scripts.
Administrator prompts of its own. It installs for your own account and runs with your normal rights; only an installer you launch may ask.
The least contrast of any text against its background, in light and dark, checked by a test.