Jenkins to MySQL Integration

How Datrise loads Jenkins into MySQL

Datrise syncs Jenkins's jobs, builds, stages, test results, artifacts, and build logs into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Jenkins: Self-hosted build automation and CI jobs.

MySQL: Widely used OSS relational engine (InnoDB).

How Jenkins entities map to MySQL

Jenkins entity	MySQL object	Notes
jobs	`jenkins_jobs`	id PK · custom fields → JSON columns
builds	`jenkins_builds`	id PK · linked to jenkins_jobs
stages	`jenkins_stages`	id PK · linked to jenkins_jobs
test results	`jenkins_test_results`	id PK · linked to jenkins_jobs

FAQ

How does Datrise handle Jenkins's custom fields in MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the Jenkins to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Jenkins to MySQL the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.