A ticket, from issue to deploy
fleet reads the Git host's issues, starts a worker for each ready ticket, merges the work and follows it to a release. The dispatcher starts the workers, the merge train or the trunk guard merges, and the keeper moves what is stuck. A lead agent or a person can still do any of these steps by hand. The Work page shows every ticket by stage. The older Builds panel joins the issues, the pull requests and the agents on one page.
Deploy stays a separate step, outside fleet: a person or a pipeline does it, and the Deployed vs HEAD panel shows what runs.
With a lead agent and issues
What fleet does and does not do
| Step | Who | Fact |
|---|---|---|
| The issue and its wave | Person | The Builds panel groups issues by the label <prefix><wave>, default wave: (fleet/internal/dash/builds.go) |
| The link to the agent | The spawner | fleet spawn --ticket owner/repo#N, repo#N or #N |
| The link to the PR | The worker | The PR text says closes, fixes or resolves #N |
| Deploy | Person or a deploy pipeline | Not done by fleet. The Deployed vs HEAD panel only shows what runs. |
- The state
mergedin the Builds panel means that the issue is closed. It does not prove that a PR merged. heldanddeferredin the Builds panel are labels that a person puts on the issue.