CLI command
probierz schedule release
What a `store` schedule runs: the product's iPhone journeys, when the App Store sells a version the schedule has not seen.
Invocation#
probierz schedule release <NAME> --app <APP> --host <HOST> --link <APP STORE LINK>Required inputs and options#
<NAME>is the schedule that fired;--appthe product;--hostthe Stado host its journeys are submitted to;--linkthe app's App Store page.
Output and state effects#
Reads the version on sale from Apple's lookup, as probierz store show reads it. A version this schedule has not seen runs every journey of the product's mobile:ios surface through probierz remote run, with --env BUNDLE_ID=<the link's bundle ID>, so a phone holding the release from the store drives it. The first firing records the version and runs nothing; the same version runs nothing again. The version is kept in the schedule's state, beside a main schedule's revisions, under app-store. Prints the schedule, product, link, bundle ID, version, the version seen before, whether this is the first release seen, the journeys and each run with its target, exit and answer.
Exact refusals#
link-invalid,release-unreadableandsurface-missingas forschedule add --trigger store;app-unknownandlookup-unanswered(exit 69) ofprobierz store showwhen Apple's lookup holds no such app or does not answer. Nothing is run or recorded after any of them. Real test: tests/schedule/release.rs.state-invalidandstate-unwritableas forschedule tick.runs-failed(exit 1): a journey whose run did not pass is named with its target, how it ended and its sentence; the new version is still recorded.
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.