kata-containers/ci-dashboard

GitHub Actions CI Dashboard

Hosted by OpenInfra Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kata-containers/ci-dashboard has 10+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 54 minutes ago
Added to GitGenius on October 15th, 2026
Created on November 28th, 2025
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 10
Total Stargazers: 5 (+0)
Total Subscribers: 0 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kata Containers CI Dashboard is a real-time monitoring dashboard for GitHub Actions CI test results.

The tool solves the problem of tracking test stability across nightly CI runs for the Kata Containers project. It fetches nightly workflow results from GitHub Actions every three hours, filters jobs by configured categories such as GPU and TEE tests, parses test output to extract failure details, and displays the results alongside a ten-day history showing test stability trends. Users can click through to specific GitHub Actions jobs for deeper investigation.

The dashboard suits teams running nightly CI suites who need visibility into test health over time without manually checking GitHub Actions. It is specifically designed for the Kata Containers project structure but can be adapted to other projects by editing the configuration file to specify job patterns and test sections. The tool is configured entirely through a YAML file, making it straightforward to add new test categories or modify existing ones without code changes.

Development activity shows consistent maintenance focused on operational reliability. The project accepts contributions for adding new tests via configuration, modifying the user interface, or enhancing data processing logic. The workflow can be manually triggered to refresh data on demand, and the dashboard automatically rebuilds when new data is committed.