Oore CI
CLI

`oore build watch`

Follow a build to its result and, with --store, to the store’s answer.

oore build watch <BUILD_ID> [--store] [--interval SECONDS]
                 [--daemon-url <URL>] [--token <TOKEN>] [--json]

The command checks the build with GET /v1/builds/{build_id} and prints a line each time it moves. A build that uploaded to Google Play or the App Store also says where its release stands, because a build succeeds once the store has the upload, not once the app is live. It needs a signed-in session (oore login, --token, or OORE_SESSION_TOKEN) that can see the build.

OptionEffect
--storeAfter the build succeeds, keep watching until the store is done: live, rejected, failed, or blocked until someone acts.
--interval SECONDSSeconds between checks, from 2 to 3600. Defaults to 10.
--daemon-urlBackend URL; otherwise uses environment, CLI config, then loopback.
--tokenSession token; otherwise OORE_SESSION_TOKEN or the stored session.
--jsonPrint nothing while waiting, then the build as JSON once it settles. Its release_outcome field holds the store’s answer.
oore build run --pipeline pipe_123 --workflow release --json | jq -r .id \
  | xargs oore build watch --store
Build #48 running
Build #48 succeeded, waiting on the store
Build #48 succeeded, in store review
Build #48 succeeded, live in the store

The release part of the line is one of: waiting on the store, blocked by the store, in store review, approved, not released yet, rejected by the store, live in the store, or store release failed. When a build has several store releases, the line names the one that most needs a person.

Exit codeMeaning
0The build succeeded and, with --store, the store took it.
1The build failed, timed out, was canceled or expired.
3With --store: the store blocked, rejected or failed it.

App Store review can take a day or more. Run --store where a long wait is fine, or check the build page instead.