Jenkins to Spreadsheets Integration

How Datrise loads Jenkins into Spreadsheets

Datrise syncs Jenkins's jobs, builds, stages, test results, artifacts, and build logs into Spreadsheets as a tab per source entity. Flexible or custom fields land in JSON-stringified cells for nested fields, and timestamps such as created, updated, and status changes are typed as ISO-8601 text or serial date cells.

Sync is incremental: Datrise uses refreshes the tab's rows each run, preserving header order, so re-runs update only what changed. Sheets caps out around the low millions of cells, so Datrise lands a curated column set rather than every raw field.

Ideal for lightweight, shareable reporting for non-technical teams.

Endpoints

Jenkins: Self-hosted build automation and CI jobs.

Spreadsheets: Business-friendly spreadsheet destination for collaborative analysis.

How Jenkins entities map to Spreadsheets

Jenkins entity	Spreadsheets object	Notes
jobs	`jenkins_jobs`	id PK · custom fields → JSON-stringified cells for nested fields
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 Spreadsheets?

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

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

It runs incrementally — Datrise uses refreshes the tab's rows each run, preserving header order.

Related pipelines

Early access

Connect Jenkins to Spreadsheets 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.