Fleet docs v0.2.0-rc.448

Builds

Each build is a set of issues in one repo, put in waves by a label. The panel shows each issue with its state, its pull request and its agent.

How to read it

  • One block for each build: its name, its repo, and a bar "closed/total · percent".
  • One block for each wave, with the same bar. A wave with open issues starts open.
  • One row for each issue: its state, #N (a link), the title, PR #N and agent <name>. agent <name> selects that agent in the agent graph.
State Colour It means
merged Green The issue is closed. It does not prove that a PR merged.
held Yellow The issue has the label held
deferred Yellow The issue has the label deferred
blocked Red Its live agent is blocked or needs_input
PR open Grey An open PR says closes, fixes or resolves #N
worker running Grey A live agent has this ticket
not started None None of these

The first state that matches wins, in the order of the table.

How often it reads

Every 60 s the server reads each build's open pull requests and the issues that changed since its last read (since=). It reads the whole issue list once an hour, which also drops a deleted issue (#443).

Turn it on

Set builds_file in serve.yaml to a JSON list of {name, repo, provider, label_prefix, min, max}. provider is github or forgejo. The issues from min to max are part of the build. The label prefix is wave: by default. Spawn each worker with --ticket repo#N. Only admins see this panel. A bad file stops the server start.

When it looks wrong

You see It means Do this
"no builds configured" The file is an empty list Add a build
"no tracker for provider …" The provider is not set up, for example forgejo with no forgejo_url Set forgejo_url in serve.yaml
"tracker status: GET /repos/…: 404 Not Found" The repo name is incorrect, or the token cannot read it Fix repo. Give a token in GITHUB_TOKEN or FORGEJO_TOKEN.
An issue says not started, but a worker runs The agent's --ticket does not match the issue Spawn with --ticket owner/repo#N, repo#N or #N
An issue says merged, but no PR merged Someone closed the issue Read the issue
An issue is not in any wave It has no wave: label, or its number is out of min..max Add the label, or change the range

Code: fleet/internal/dash/builds.go, fleet/internal/dash/builds_rest.go. See a ticket to deploy.