Integrations

Connect the tools you already use. Each integration is a focused setup guide: what events you get, how to wire it up, and where the data lands.

Collect Events From

Track repository, pipeline, and deployment activity as CDEvents — which subject each source can emit, toggle to see the predicates:

Source	artifact	branch	change	repository	pipelineRun	taskRun	testSuiteRun	service	environment	incident	ticket
GitHubWebhook, REST API (polling), Action (send-cdevents), Actions CI (send --run)	✓published, packaged	✓created, deleted	✓created, merged, abandoned, updated, reviewed	✓created	✓queued, started, finished	✓started, finished	✓finished, started	✓deployed	✓created		✓created, closed, updated
GitLabWebhook, CI (send --run)	✓published	✓created, deleted	✓created, merged, abandoned, reviewed, updated		✓queued, started, finished	✓started, finished	✓started, finished				✓created, closed, updated
Bitbucket	✓published	✓created, deleted	✓created, updated, reviewed, merged, abandoned		✓started, finished						✓created, updated, closed
Forgejo	✓published	✓created, deleted	✓created, merged, abandoned, updated, reviewed	✓created	✓queued, started, finished						✓created, closed, updated
Gitea	✓published	✓created, deleted	✓created, merged, abandoned, updated, reviewed	✓created	✓queued, started, finished	✓started, finished					✓created, closed, updated
Jenkins						✓started, finished	✓started, finished
ArgoCD								✓deployed, removed		✓detected
Kubernetes								✓deployed, removed, upgraded
Jira	✓published										✓created, updated, closed
Test & Quality ReportsJUnit XML, TAP, SARIF							✓started, finished
CDEvents	✓published, signed, packaged, downloaded, deleted	✓created, deleted	✓created, updated, reviewed, merged, abandoned	✓created, modified, deleted	✓queued, started, finished	✓started, finished	✓queued, started, finished	✓deployed, upgraded, rolledback, removed, published	✓created, modified, deleted	✓detected, reported, resolved	✓created, updated, closed

A row covers all the integrations listed under it: a subject may be emitted by only some of them — hover a cell, or open the integration page, to see which.

• GitHub Webhook — repository, PR, and workflow events with signature validation
• GitHub Action — send hand-crafted CDEvents from workflow steps
• GitHub Actions CI — test and task reporting from CI jobs
• GitHub REST API (Polling) — backfill and pull-based tracking without webhooks
• GitLab Webhook — repository, MR, and pipeline events
• GitLab CI — test and task reporting from CI jobs
• Bitbucket Webhook — repository, PR, issue, and commit status events (beta)
• Forgejo Webhook — repository, PR, issue, release, package, and Actions events
• Gitea Webhook — repository, PR, issue, release, package, and Actions events
• Jenkins — job and pipeline events
• ArgoCD — GitOps deployment events via notifications
• Kubernetes (via Kubewatch) — cluster deployment events
• Jira — ticket and version events (beta)
• CDEvents — any native producer, agent, or proxy sending CDEvents (v0.3–v0.5) to the webhook

Report Test & Quality Results

Emit testSuiteRun CDEvents from any CI job with cdviz-collector send --run:

• JUnit Reports — Maven, Gradle, pytest, and any tool producing JUnit XML
• TAP Reports — Node test runner, bats, shellspec, and any TAP producer
• SARIF — linters, static analysis, and security scanners

Store & Visualize

• PostgreSQL — the CDviz event store (TimescaleDB hypertable, DORA views)
• ClickHouse — alternative analytics storage via the ClickHouse sink
• Grafana — pre-built dashboards for DORA metrics, deployments, and incidents

Trigger Automation

React to the event stream — see Event Reaction for all patterns:

• Argo Workflows — submit workflows from CDEvents (post-deployment tests, environment promotion, artifact validation)

Something Else?

The collector is open source and extensible — see Custom Integration to connect any tool via webhooks, polling, and VRL transformers.