Changelog
What's new
Recent releases have made the window say what it means: long output lines wrap, tabs line up, the update check is described exactly and each button is named for what it does. Before that came a typical build time on every row and a Launch installer button that finds the setup program a build produced. The first release brought the deck itself: builds remembered, run side by side, watched live and stopped with everything they started.
v1.3.1
Buttons named for what they do
- Hovering a row's play button now reads "Build" followed by the row's name, since it runs that row's build steps; the Guide's entry is renamed to match
- In the Edit dialog a screen reader now announces the step order buttons as "Move the selected step up" and "Move the selected step down", since they run nothing
v1.3.0
The update check, described exactly
- The Guide, the README, the website and the requirements now say that the daily update check names BuildPilot and its version, because GitHub asks every caller to identify itself
- It still carries nothing about you or your scripts; it remains the only network request BuildPilot makes
- DECISIONS-TRADEOFFS.md sets out the deliberate choices BuildPilot rests on, with what each one gains and costs
v1.2.2
Long output lines are no longer cut off
- A line wider than the output tray now wraps onto as many lines as it needs, breaking at a space where it can, so tools such as Nuitka no longer lose the end of almost every line
v1.2.1
Tabs in output no longer show as boxes
- A tab in a script's output now becomes spaces up to the next tab stop, so the columns of go test line up as they do in a terminal
- Any other control character a script prints, such as a bell, is left out rather than drawn as a box
v1.2.0
Typical build time
- Every row shows how long its build usually takes, on a line of its own beneath the status, so there is something to judge a running build against
- The typical time is the median of the last five successful runs: one slow build on a cold cache does not move it; a failed or stopped run does not count
- It shows in every state, Not run included; it is remembered across restarts in run-times.json beside your settings file, which is unchanged
- Removing an operation forgets its run times; a run times file that cannot be read or written is noted in the log and the typical times start afresh
v1.1.0
Launch installer
- Each row has a Launch installer button right of Stop, starting the project's setup program as Explorer would, so Windows asks for administrator rights where the installer needs them
- BuildPilot finds the installer itself: the working directory's name followed by Setup.exe, in dist-installer or dist. The Edit dialog's new Installer field sets one named differently
- The button is greyed, with the reason in its tooltip, when there is nothing to launch, while the row runs and after a run that failed or was stopped
- The Edit dialog's step buttons now sit two by two beside the steps, so the dialog fits the window at its usual size
- The output tray now stays on the last line while it follows a run, so the green, red or grey closing line is always in view at the end
v1.0.1
The selected row stays in sight when the tray opens
- Opening or growing the output tray no longer hides a row selected near the foot of the list; the list scrolls just far enough to keep it in view
v1.0.0
The first release: a flight deck for your build scripts
- An operation is one or more steps run in order in a working directory; PowerShell, batch, executable and Python scripts run out of the box and Settings maps any other file type to its program
- Every step's script is checked before the first one starts, so a missing script is found before a long first step rather than after it
- Add takes a script or a folder and proposes ready-made operations for projects holding build.ps1 or buildexe.py then buildinstaller.py; nothing is added until you confirm
- A Python or PowerShell step runs inside the working directory's virtual environment, with any inherited environment undone first; BuildPilot never creates or changes one
- Run the ticked builds starts every ticked row at once; two builds never run in the same folder. The output tray follows each run live and the exit code decides the outcome
- Every run starts in its own Windows job object, so Stop ends the script and every process it started
- Every control is reachable with Tab and the arrow keys and wears a visible focus ring; light and dark themes follow Windows
- One network request: a check for a newer release shortly after opening and once a day
- BuildPilotSetup.exe installs for your own account only, so Windows never asks for administrator rights; uninstalling keeps your operations and settings unless you untick that