Originally reported by DevOps.com, May 2020.
Overview
In May 2020, CircleCI announced a set of platform updates spanning analytics, user interface design, Docker convenience images, and API improvements. The changes were aimed at giving DevOps teams better visibility into pipeline performance and a faster, more intuitive experience when managing CI/CD workflows.
Buildtrakr: Analytics Plugin Built with Plandek
CircleCI partnered with analytics company Plandek to launch Buildtrakr, a plugin designed to surface meaningful engineering performance data from within the CircleCI platform. Buildtrakr integrates with both CircleCI and Git to synthesize commit history and build performance data, presenting key metrics through a unified dashboard.
The goal of the plugin is to give engineering leaders and DevOps teams a clearer picture of delivery pipeline health — including build frequency, failure rates, and cycle time — without having to export data to external tools manually.
Revamped User Interface
CircleCI also shipped a significant redesign of its web interface. According to CircleCI CEO Jim Rose, the primary driver was making pipeline status easier to understand at a glance, particularly for teams running complex, multi-stage workflows.
Key changes to the UI include:
- Pipeline-level status view: Users can now see the state of entire pipelines without having to drill into individual jobs.
- Filterable build list: A filterable view with nested workflow and job information makes it faster to scan the status of recent builds.
- Improved job detail pages: Redesigned to present more digestible output, including full-screen step logs for easier debugging.
- Cleaner config-as-code view: Configuration files are displayed in a more readable format within the UI.
- Faster load times: Rose reported a 65% reduction in page load times as part of the redesign.
New Docker Convenience Images
CircleCI reconfigured its fleet of CircleCI convenience images — pre-built Docker images optimized specifically for continuous integration environments. According to Rose, the updated images are faster to pull, easier to download, and provide a more efficient foundation for building custom images on top of.
New convenience images were released for a range of programming languages, including:
- Python
- Ruby
- Rust
- Go
- Several additional languages
These images ship with improved documentation, greater stability, and more efficient underlying infrastructure. Importantly, each convenience image is maintained as an individual open source project, meaning they can be used in any CI/CD environment — not exclusively on the CircleCI platform.
Insights API: Date Range Parameters for Workflows and Jobs
CircleCI also updated its Insights API endpoints to support start and end date parameters for both workflows and jobs. These parameters allow teams to restrict the range of executions returned based on their start times, making it easier to query specific time windows for reporting and analysis. A new filter was also added to support more targeted testing analysis.
Context: Remote Work and the Shift to Cloud-Based CI/CD
Rose noted that platform activity on CircleCI had increased in cloud environments in the wake of the COVID-19 pandemic. With engineers working remotely and unable to access on-premises infrastructure, reliance on physical build servers — the proverbial “build box under someone’s desk” — became untenable. Cloud-hosted CI/CD platforms saw increased adoption as a result.
The broader trend reinforces a long-standing argument for cloud-native CI/CD: that build infrastructure should be elastic, remotely accessible, and decoupled from physical office environments. The pandemic accelerated that realization for many organizations that had previously deferred the migration.
The Role of Metrics in Mature DevOps Practices
Underlying all of these updates is a recognition that metrics and observability are becoming central to how DevOps teams operate. Analytics tools like Buildtrakr are most valuable when they are used to identify bottlenecks and coach improvement — rather than simply measuring output volume. The goal of a healthy CI/CD pipeline is not to ship more code faster in raw terms, but to deliver higher-quality software reliably and at the right cadence.
As organizations build and deploy more customer-facing digital applications, the ability to tie engineering metrics to business outcomes will only grow in importance.