Build Matrix Cleanup: Remove CI Jobs for Targets You No Longer Ship

Build matrix cleanup starts when CI still tests runtimes, operating systems, architectures, browser versions, or feature combinations the product no longer ships. The waste is not just minutes; stale matrix rows can hide which targets are actually supported.

The useful output is a build matrix cleanup pull request with support evidence, removed targets, release-output checks, and CI results. Keep the review concrete: Update the support policy before deleting the CI row, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when deleting coverage for a platform or runtime that still has supported users.

Key takeaways

Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
Use one release cycle plus the longest promised platform support window before deciding that “quiet” means “unused.”
Prefer reversible changes first when deleting coverage for a platform or runtime that still has supported users is still plausible.
Leave behind a build matrix cleanup pull request with support evidence, removed targets, release-output checks, and CI results so the next review starts with context.
Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.

Map Supported Targets

Start with one workflow matrix across supported platforms, release artifacts, package metadata, customer commitments, test failures, and cache behavior. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.

Field	Why it matters
Owner	Cleanup needs a person or team that can accept the decision
Current purpose	A short reason to keep the item, written in present tense
Last meaningful use	owners, callers, last change, runtime behavior, and deletion confidence
Dependency evidence	repository search, tests, logs, deploy history, and owner review
Risk if wrong	The outage, data loss, access failure, or rollback gap the review must avoid
Next action	Keep, reduce, archive, disable, remove, or investigate

Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.

Matrix Evidence to Review

The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For build matrix cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Support policy	Runtime versions, OS targets, browser matrix, package engines, and customer commitments	The matrix row no longer maps to a supported target
Release output	Artifacts, installers, container tags, packages, and deploy jobs produced by the target	No release process consumes the row
Failure value	Recent failures, flakes, quarantines, and defects caught only by that target	The job no longer catches unique risk
Cost and cache shape	Queue time, runner class, cache hit rate, artifact size, and retry rate	The row burns capacity without improving confidence

Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.

If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.

Example Evidence Check

Search CI matrix rows beside support policy and release artifacts before removing a target.

rg "matrix:|node-version|python-version|os:|browser" .github .gitlab ci
rg "supported versions|LTS|runtime|platform" README* docs package.json
rg "upload-artifact|release|publish|installer" .github scripts

Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.

Remove One Target Group

Use the least permanent move that proves the decision. In build matrix cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.

Update the support policy before deleting the CI row.
Remove one target group at a time and watch release artifact generation.
Keep a periodic compatibility job if daily coverage is no longer justified.

Track the cleanup candidate with a simple priority score:

Score	Good sign	Bad sign
Impact	Meaningful spend, risk, toil, noise, or confusion disappears	The item is cheap and low-risk but politically distracting
Confidence	Owner, purpose, and dependency path are understood	The team is guessing from age or name
Reversibility	Restore, recreate, re-enable, or rollback path exists	Deletion would be the first real test
Prevention	A rule can stop recurrence	The same pattern will return next month

Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.

Jobs That Still Ship Artifacts

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

Long-term-support runtimes, regulated customer platforms, and self-hosted deployments.
Matrix rows that build release artifacts even when their tests look redundant.
Jobs that catch packaging, locale, architecture, or browser-specific failures.

For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.

Run the CI Matrix Change

Run build matrix cleanup as a decision review, not an open-ended hygiene project.

Pick the narrow scope and export the candidate list.
Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
Apply the least permanent useful change first.
Watch the signals that would reveal a bad decision.
Complete the final removal only after the review window closes.
Save a build matrix cleanup pull request with support evidence, removed targets, release-output checks, and CI results.

For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.

Tie Jobs to Support Policy

Prevention should change the creation path, not just the cleanup path. For build matrix cleanup, the useful prevention fields are owner, reason to exist, removal trigger, and verification notes. Make those fields part of normal creation and review.

Tie every matrix row to a support policy entry and removal trigger.
Expire temporary migration targets when the compatibility window closes.
Review CI targets alongside runtime upgrades and customer support changes.

The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.

Example Decision Record

Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.

Field	Example entry for this cleanup
Candidate	Stale CI build matrix jobs in CI pipelines
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Support policy, Release output, and owner confirmation
First reversible move	Update the support policy before deleting the CI row
Watch signal	The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong
Final action	Keep, reduce, archive, disable, or remove after one release cycle plus the longest promised platform support window
Prevention rule	Tie every matrix row to a support policy entry and removal trigger

This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.

FAQ

How often should teams do build matrix cleanup?

Use one release cycle plus the longest promised platform support window for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.

What is the safest first action?

The safest first action is usually ownership repair plus evidence collection. After that, update the support policy before deleting the ci row. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to long-term-support runtimes, regulated customer platforms, and self-hosted deployments. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.

How do you make the decision useful later?

Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.