TECHPARTNER CONSULTING

Codester demo · Business software

BuildPilot — Build and Deploy Automation

Build, test, and deploy jobs and pipelines on your own machine — every run recorded, no per-seat CI bill.

$99 on CodesterPipelines, jobs, and build agentsRuns on your own machine with Docker

Boot test status — stated plainly

The packaging boot test is deferred: this build machine's container store refused the pinned program image build twice with the same write fault (the sandbox's known intermittent store fault — the exact errors are in the test record below), so no container was started and no boot is claimed. What was verified from a fresh extraction of the shipped package: the pinned image exists on the registry, the pinned plugin versions exist in the official plugin directory, the install files parse and agree with each other, the starter pipeline script is structurally valid, and every claim in the listing was checked against the package. Screenshots of the dashboard and a green starter-pipeline build will be added when the boot test is closed on a normal Docker host; none are shown here because none were honestly captured.

Boot test record

Real lines from the packaging boot test: the pin and license verified, the image manifest checked, and the exact store fault that deferred the boot — nothing dressed up.

Pin: program release 2.580.2 (LTS), commit ea3f958268fe87ed86a5d1c2d90c5a99426b97ce
License in clone: MIT (LICENSE.txt — "The MIT License")
Boot state: DEFERRED — sandbox store fault. No container was started and no boot is claimed.
level=error msg="Removing store for partially-created runtime: write /home/hatch/podman-vfs/vfs-layers/.tmp-layers.json...: operation not permitted"
Error: failed to open 2048 locks in /libpod_lock: operation not permitted

What it does