DevLake Domain Model#

The domain model is DevLake's source-agnostic data layer — the normalized, tool-independent schema that all plugins write into after extracting and converting raw data. It lives under backend/core/models/domainlayer/ and is organized into six sub-packages 1:

Base Structs and Embedding Hierarchy#

Every domain model struct embeds the same chain 2 3:

DomainEntity / DomainEntityExtended
  └── common.NoPKModel
        ├── CreatedAt, UpdatedAt (time.Time)
        └── RawDataOrigin
              ├── _raw_data_params (index for flushing stale records)
              ├── _raw_data_table
              ├── _raw_data_id
              └── _raw_data_remark

• DomainEntity — string primary key (Id) in the format <Plugin>:<Entity>:<PK0>:<PK1>…, enabling cross-plugin deduplication.
• DomainEntityExtended — same structure but varchar(500) for longer IDs.
• NoPKModel — embeds RawDataOrigin, which records the source raw table and row ID for each domain record (used for debugging and incremental sync).
• Tool-layer models (plugin-private tables) embed common.NoPKModel or common.Scope directly, without the string primary key.

DORA-Relevant Tables#

cicd_deployments#

CICDDeployment stores one row per deployment. Key fields:

• Environment / OriginalEnvironment — normalized value (e.g., PRODUCTION) and the raw label from the tool 4
• Result / Status — normalized outcome (SUCCESS, FAILURE) and run state 5
• TaskDatesInfo (embedded) — CreatedDate, QueuedDate, StartedDate, FinishedDate
• DurationSec, QueuedDurationSec

cicd_deployment_commits#

CicdDeploymentCommit is the primary join between deployments and the commit graph. It carries all CICDDeployment fields plus:

• CommitSha — part of the composite primary key alongside Id 6
• RepoId, RepoUrl — links the deployment to a repository 7
• PrevSuccessDeploymentCommitId — populated by the DORA enricher to bound commit-diff ranges for Lead Time calculation 8
• ToDeployment() helper converts a commit row back to a CICDDeployment

project_pr_metrics#

ProjectPrMetric stores per-PR lead-time decomposition. Composite primary key: Id + ProjectName.

incidents#

Incident is populated from two upstream sources: issues tables and pull_requests (via PullRequest.ToIncident()) 9. Key DORA fields:

• CreatedDate, ResolutionDate — used for Mean Time to Restore (MTTR) calculation 10
• LeadTimeMinutes — pre-computed duration 11
• Table + ScopeId — composite index that records the source table and scope 12

project_incident_deployment_relationships#

Links each incident to its nearest prior deployment within a project, enabling Change Failure Rate (CFR) calculation. See crossdomain/project_incident_deployment_relationship.go.

dora_benchmarks#

doraBenchmarkBasic (dora_benchmarks table) stores reference thresholds for rating teams against DORA report norms. Fields: Metric, Low, Medium, High, Elite, DoraReport. Seeded by the migration script with rows for both the 2021 13 and 2023 14 DORA reports. The 2023 report renamed "Time to restore service" → "Failed deployment recovery time" and tightened all thresholds 15.

Migrations#

Schema evolution for DORA-specific tables lives in backend/plugins/dora/models/migrationscripts/. Each migration file:

• Is named with a date prefix (e.g., 20240223_add_dora_2023_benchmark.go)
• Implements Up(basicRes) error, Version() uint64, and Name() string 16
• Uses migrationhelper.AutoMigrateTables() to run GORM's AutoMigrate and record the run 17
• Uses archived.Model (numeric ID) for the in-migration struct definitions — distinct from the string-ID DomainEntity used at runtime

All migrations are registered in register.go.

Key Source Files#