DEVOPS

Merge-Request CI Cache-Hit Coach

When a merge request's pipeline finishes, analyzes its job cache-hit rates and runtime.

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab MR pipeline-completed webhookGitLabGitLab
  • ActionFetch job logs and cache metadataGitLabGitLab
  • LogicCompute cache-hit rate; flag inefficient MRs only
  • ActionDraft caching coaching with .gitlab-ci.yml fixesOpenAI
  • OutputPost coaching comment on the merge requestGitLabGitLab

What it does

Gives developers immediate, in-context feedback on the CI efficiency of their own merge request — surfacing low cache-hit rates and slow stages right where they work, so caching improvements ship with the code rather than as a later cleanup.

When to use it

When you want to push cost-awareness left to the moment of authoring, instead of relying on a central platform team to retrofit caching. Great for teams adopting a 'you build it, you tune it' culture.

How it works

  1. 1A GitLab webhook triggers when a merge-request pipeline completes.
  2. 2The flow fetches the pipeline's job logs and cache metadata from the GitLab API.
  3. 3A logic step computes per-job cache-hit rate and total wall-clock time, flagging the MR only if hit rate is low or runtime exceeds the project median.
  4. 4An OpenAI step drafts concise, friendly coaching with exact .gitlab-ci.yml cache key suggestions.
  5. 5The advice is posted as a comment on the originating merge request.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.