circus/crates/common/migrations
NotAShelf 8d07063d3f
db: add migration 008 for user management tables
Signed-off-by: NotAShelf <raf@notashelf.dev>
Change-Id: I99349ba4b389b525d66d0109a66243736a6a6964
2026-02-05 22:45:08 +03:00
..
001_initial_schema.sql meta: add database migrations; set up migration CLI 2026-02-02 01:15:00 +03:00
002_add_build_system.sql crates: production models and repo layer 2026-02-02 01:15:05 +03:00
003_production_features.sql crates: production models and repo layer 2026-02-02 01:15:05 +03:00
004_build_outputs_and_deps.sql crates: production models and repo layer 2026-02-02 01:15:05 +03:00
005_channels_remote_builders.sql crates: production models and repo layer 2026-02-02 01:15:05 +03:00
006_hardening.sql crates: production models and repo layer 2026-02-02 01:15:05 +03:00
007_branch_and_scheduling.sql crates/common: add migration for multi-branch eval and scheduling shares 2026-02-02 01:49:25 +03:00
008_user_management.sql db: add migration 008 for user management tables 2026-02-05 22:45:08 +03:00
README.md meta: add database migrations; set up migration CLI 2026-02-02 01:15:00 +03:00

Database Migrations

This directory contains SQL migrations for the FC database.

Migration Files

  • 001_initial_schema.sql: Creates the core database schema including projects, jobsets, evaluations, builds, and related tables.

Running Migrations

The easiest way to run migrations is to use the vendored CLI, fc-migrate. Packagers should vendor this crate if possible.

# Run all pending migrations
fc-migrate up postgresql://user:password@localhost/fc_ci

# Validate current schema
fc-migrate validate postgresql://user:password@localhost/fc_ci

# Create a new migration
fc-migrate create migration_name

TODO: add or generate schema overviews