Skip to content

Getting started

DV Forge takes the results of your simulation regressions and groups every failing job into signatures: one signature per distinct failure, across tests, seeds and regressions. Your team then triages signatures instead of individual failing jobs, automates repeat decisions with rules, and asks the root-cause agent for a hypothesis. This page covers the core ideas on one screen. After reading it you'll know what each term in the app means and where to go next.

How results flow

flowchart LR
  CI["Your CI or regression farm"] -->|dvforge upload| DP["Data plane<br/>(optional, in your network)"]
  CI -.->|dvforge upload| DVF
  DP -->|"results, redacted excerpts"| DVF["DV Forge"]
  DVF --> R["Regressions<br/>and failures"]
  R --> S["Signatures"]
  S --> T["Triage<br/>and rules"]
  T --> A["Root-cause<br/>agent"]
  1. Your CI runs the regression and calls dvforge upload with the JUnit results and the simulation logs.
  2. The upload goes straight to DV Forge or, if your project uses one, to a data plane in your own network. The data plane keeps the raw logs and forwards only structured results, redacted excerpts and each failure's headline.
  3. DV Forge records the regression and its jobs, extracts a headline from each failing job, and files the failure under a signature.
  4. Your team triages signatures: sets their status, assigns owners, links bugs. Triage rules do the repetitive part automatically.
  5. The root-cause agent investigates a signature and proposes a hypothesis. A person (or a rule) confirms it.

Core ideas

Organization
Your company's account in DV Forge. People belong to an organization with one role, and that role applies to every project in it.
Project
The container for results. Regressions, signatures, rules, labels and API tokens all belong to exactly one project. You refer to a project as org-slug/project-slug. See Projects, roles and tokens.
Regression
One run of your regression suite, such as a nightly, uploaded as a unit and identified by an external id you choose (usually the CI build id). It's live while uploads arrive and complete once the upload finishes. See Regressions and failures.
Simulation job
One test with one seed inside a regression. It has a status (pass, fail, error, timeout, killed or skipped) and, optionally, a log. See Regressions and failures.
Failure
A job that didn't pass (fail, error, timeout or killed), with the headline message DV Forge extracted from its log. See Simulators and log formats.
Signature
A project-wide group of failures that share the same fingerprint, so the same bug in different tests, seeds and regressions is one signature. See Signatures.
Triage status
Where a signature is in its lifecycle: Untriaged, Investigating, Root-caused, Tracked, Resolved, Regressed, Muted, Not a bug or Waived. See Triage.
Rule
Project automation. When a signature appears, is hit, comes back or regresses (and on a few other events), matching rules set its status, assign it, label it, link a bug, notify people or run the agent. See Triage rules.
Data plane
An optional service you run in your own network. It receives uploads, keeps raw logs, and connects out to DV Forge only. DV Forge fetches a full log from it only when someone opens that log. See Data planes.
Run
One investigation by the root-cause agent. A finished run leaves a hypothesis on the signature, but doesn't change the signature's status. See Runs and hypotheses.

The Glossary defines the rest of the vocabulary.

Where to go next

You are… Start with
A DV engineer who triages failures Quickstart, then Working a signature
Setting up uploads from CI The dvforge CLI and CI integration
A verification lead The triage queue and Triage rules
An administrator Administration