CLI command
probierz schedule tick
What a `main` schedule runs: the journeys a new main revision of one product's repositories, or of every product's, touches.
Invocation#
probierz schedule tick <NAME> [--app <APP>] --host <HOST>Required inputs and options#
<NAME>is the schedule that fired;--appthe product;--hostthe Stado host the touched journeys are submitted to.- Without
--appthe tick covers every product whose manifest the workspace holds at this firing, so a repository that gains a manifest is covered from the next firing. Each product is ticked on its own, as with--app, and keeps its revisions inschedules/<NAME>/<app>.jsonof the state directory, so two products mapping one repository each see its change; the host budget is read once per firing and spent across every product. The answer is{schedule, products}, one tick's answer per product, or{appId, refused}for a product that could not be ticked. - A firing holds the schedule's lock,
locks/schedule-<NAME>.lockof the state directory, while it ticks. A firing that meets an earlier one still holding it runs and records nothing and answers{schedule, held}with exit 0; the kernel drops the lock of a firing that dies.
Output and state effects#
Fetches each repository the manifest names, diffs a main revision this schedule has not seen against the one it saw, and submits every journey those files touch through probierz remote run, riskiest first (critical, then red, then the rest). A journey whose newest duration does not fit what is left of budget.host-seconds-per-day (held against the whole instance's host time of the day) is skipped and kept as skipped, never shown green. A journey green before the tick and red in it is listed under turnedRed; with bisect.on-red set to bisect each is bisected on the schedule's host (probierz bisect <app> <journey> --host <host>) and its answer kept under bisected, else the answer says how to turn it on. The revisions are recorded in the state directory; the first tick records them and runs nothing. An unreadable state file is refused naming it, never taken for a first tick.
Exact refusals#
- Each before anything runs or is recorded:
main-untracked(exit 1), a main that tracks no remote branch, naming thegit branch --set-upstream-tothat fixes it;fetch-failed(exit 69, worth retrying), a remote that cannot be fetched, with git's answer;diff-failed(exit 1), a recorded revision the checkout does not hold;state-invalid(exit 1), a state file that holds no revisions, never taken for a first tick;lock-unopened(exit 1), a lock file that cannot be opened or locked, named. Real test: tests/schedule/main/tick.rs. state-unwritable(exit 1): a state file that cannot be written is refused naming it; the runs this tick started stand.runs-failed(exit 1): any run that did not pass makes the tick exit 1 naming each one with its target, how it ended and its sentence; a bisect that refused is kept with its sentence and does not change that. Without--appeach run is named with its product.products-unticked(exit 1): without--app, a product that could not be ticked (a manifest that cannot be read, any refusal above) is named with its refusal; every other product is still ticked and its revisions recorded. Real test: tests/schedule/main/every.rs.
Source snapshot#
Generated from the Rust binaries at revision 99a74945a3598a8d73b6c6cbe5aae4f283becea3 of Probierz's private source repository.
Combined help SHA-256: 77529678a61237f774b59e76df0d1907cb749ef5da56d2ed913b040793b7d30b; binary SHA-256: be9e0eaff0e6ea50403a0c6f6d467697a4eac676f9523b8dc13a596d2b5526c5.