Table: circleci_insights_workflow_run - Query CircleCI Workflow Runs using SQL

CircleCI is a continuous integration and delivery platform that automates the build, test, and deploy processes for software. The Workflow Runs in CircleCI are individual executions of a pipeline, which include one or more jobs configured in the .circleci/config.yml file. Workflow Runs provide detailed information about the execution of jobs, including status, duration, and outcome.

Table Usage Guide

The circleci_insights_workflow_run table provides insights into Workflow Runs within CircleCI. If you are a DevOps engineer or a software developer, you can use this table to monitor and analyze the performance of your software's build, test, and deploy processes. The table can also aid in identifying any issues or bottlenecks in these processes, thereby helping you optimize your software's continuous integration and delivery pipeline.

Examples

Get average duration and deployment count of a project for each month

Analyze the performance of a specific project over time by determining the average duration and number of successful deployments each month. This can help assess the efficiency of the project's workflow and identify potential areas for improvement.

select
  project_slug,
  workflow_name,
  id,
  to_char(created_at, 'YYYY-MM') as year_month,
  avg(duration) as average_duration,
  count(id) as deployment_count
from
  circleci_insights_workflow_run
where
  workflow_name = 'default'
  and project_slug = 'gh/companyname/projectname'
  and branch = 'main'
  and status = 'success'
group by
  project_slug,
  year_month;

select
  project_slug,
  workflow_name,
  id,
  strftime('%Y-%m', created_at) as year_month,
  avg(duration) as average_duration,
  count(id) as deployment_count
from
  circleci_insights_workflow_run
where
  workflow_name = 'default'
  and project_slug = 'gh/companyname/projectname'
  and branch = 'main'
  and status = 'success'
group by
  project_slug,
  year_month;

List workflows created in the last 30 days

Explore the recent workflows created in your project over the past month. This is useful for tracking project progress and assessing the duration of each workflow.

select
  workflow_name,
  branch,
  id,
  project_slug,
  duration
from
  circleci_insights_workflow_run
where
  workflow_name = 'default'
  and project_slug = 'gh/companyname/projectname'
  and created_at >= current_date - interval '30' day;

select
  workflow_name,
  branch,
  id,
  project_slug,
  duration
from
  circleci_insights_workflow_run
where
  workflow_name = 'default'
  and project_slug = 'gh/companyname/projectname'
  and created_at >= date('now', '-30 day');

List workflows which are in failed state

Uncover the details of failed workflows within a specific project. This query is useful to identify bottlenecks, analyze project performance, and implement corrective measures.

select
  workflow_name,
  branch,
  id,
  project_slug,
  duration
from
  circleci_insights_workflow_run
where
  workflow_name = 'default'
  and project_slug = 'gh/companyname/projectname'
  and status = 'failed';

select
  workflow_name,
  branch,
  id,
  project_slug,
  duration
from
  circleci_insights_workflow_run
where
  workflow_name = 'default'
  and project_slug = 'gh/companyname/projectname'
  and status = 'failed';

Schema for circleci_insights_workflow_run

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form, e.g. connection_name.
branch	text	=	The VCS branch of a Workflow's trigger.
created_at	timestamp with time zone	=	Timestamp of when the workflow was created.
credits_used	bigint		The number of credits used during execution.
duration	bigint		Duration of the workflow in seconds.
id	text		Unique key for the workflow.
project_slug	text	=	A unique identification for the project in the form of: <vcs_type>/<org_name>/<repo_name>.
status	text		Workflow status.
stopped_at	timestamp with time zone		Timestamp of when workflow was stopped.
workflow_name	text	=	The name of the workflow.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- circleci

You can pass the configuration to the command with the --config argument:

steampipe_export_circleci --config '<your_config>' circleci_insights_workflow_run