DEVOPS
Detect GitLab CI cache hit-rate drops and pin the offending commit
Watches GitLab CI pipelines for a sustained drop in build-cache hit rate and, when it crosses a threshold, bisects recent commits to name the config change that caused it…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab pipeline completed webhookGitLab
- ActionParse job logs and compute cache hit rateGitLab
- ActionStore sample and load rolling baselinePostgres
- LogicHit rate below threshold for N pipelines?
- ActionRank commits in window touching cache configGitLab
- OutputPost suspected culprit commit to SlackSlack
What it does
It tracks the cache hit rate of your GitLab CI build jobs over a rolling window. When the rate falls below your baseline for several consecutive pipelines, it inspects the commits merged in that window, finds the one that touched cache-relevant config (`.gitlab-ci.yml`, lockfiles, Dockerfile, cache keys), and posts the suspected culprit with a diff link to Slack.
When to use it
Use it when CI times creep up and nobody can say why. A changed cache key, a bumped base image, or a reordered install step silently invalidates the cache and adds minutes to every build. This catches the regression within a few pipelines instead of weeks later.
How it works
- 1A GitLab pipeline-completion webhook fires after each build pipeline.
- 2The flow parses job logs for cache restore/save stats and computes the hit rate.
- 3It stores the sample in Postgres and compares the rolling average against the stored baseline.
- 4If the rate is below threshold for N consecutive pipelines, it pulls the commits in the regression window from GitLab and ranks those touching cache-relevant files.
- 5It posts the top suspect, the affected jobs, and a compare link to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.