Start a run
Starts a run of a team, in one of two ways:
- On a realm (
realm_id): CliqHub offers the run to every online daemon of the realm and the first to claim it runs it. The reply is the queue item, alreadyclaimed. - On one daemon (
daemon_id, withworkspace_idandteam_id): CliqHub sends the run to that daemon. The reply has the newrun_id.
Before sending, CliqHub checks the team’s required inputs, that the reviewers name
phases the team has, that notify_channels exist in the realm, and that every custom
agent the team uses is registered in the organization. Inputs can be sent as inputs
or run_context.inputs; run_context.id is your own correlation id.
Requires a realm operator (or higher) with the teams.run permission on the realm given by realm_id. When you target daemons with daemon_id instead, you need that role on each daemon’s realm. Token scope dispatch.
Authorizations
User PAT (cliq_tok_…, including session-scoped) or realm token (cliq_dt_…).
Body
Start the run on whichever online daemon of this realm claims it. Send this or daemon_id.
1Start the run on this daemon. Send this or realm_id; needs workspace_id and team_id.
1The team to run (id, or scope/slug on the realm path).
1Workspace to run in (daemon path: required).
1Absolute folder on the daemon, when the workspace is not known to CliqHub yet.
Run this manifest instead of the installed team's.
Display name. A name is generated when omitted.
local (default) or docker.
local, docker Higher numbers are offered first when the realm has a queue.
Team inputs by name.
Correlation id, labels stored with the run, and inputs.
Older form of the realm request; prefer the fields above.
Reviewers per human phase for this run: { phase: [username] }; replaces the team defaults for those phases
Notification channels (name or id in the run's realm) that receive this run's lifecycle events instead of the realm rules
1 - 200 elements1 - 200