Feature
Build reports and regression alerts
Every successful build prints a report and records it with the version metadata: toolchain, duration, cache mode, binary size, and a regression comparison against comparable builds. No flags, no configuration, no network.
simulated
comparing against the previous five comparable builds
What every build records
A build report captures the language and compiler version, start and end time, duration, artifact size and platform, cache status, the git commit when available, and the build arguments you passed. It lives in versions.json as an optional additive field, so older versions simply have no report.
Because the compiler version is recorded, an accidental toolchain bump is visible instead of silently changing the artifact.
simulated
recording the build · toolchain, duration, cache state, size
Comparisons that stay honest
Regression analysis compares a build against the previous five comparable builds: same app, language, toolchain, platform, and artifact type. Duration is only compared within the same cache mode, so a cold compile is never painted as a regression against a cache hit - the report says Comparison skipped instead.
Size alerts fire on growth of at least 1 MB or 5%; duration alerts fire on a slowdown of at least 25% and 2 seconds, avoiding noisy micro-changes.
Observability, not a gate
Missing history never fails a build, and a reporting problem only prints a warning. phelix build-report reads stored reports offline and read-only, which makes it usable on a server with no dashboard connection.
Frequently asked questions
Short answers; the docs go deeper.
Are build reports sent anywhere?
No. Reports are stored locally inside the app's versions.json file and work fully offline; phelix build-report inspects them without triggering a build.
Why does the report say comparison skipped?
Comparison is skipped when builds are not comparable, such as comparing a cold build's duration to a cache hit. Binary size comparisons remain valid across cache states.
One binary between git push and production.
Install the CLI, verify the host, and follow the quick start to build your first application.