CI Runner Label Cleanup: Remove Legacy Labels After Fleet Migration

CI runner label cleanup starts when jobs still request labels for hardware, operating systems, network zones, or privileged runners that no longer exist. A stale label can strand builds in queues or route sensitive jobs to the wrong fleet.

For stale CI runner labels and workflow routing rules, the review should connect current use, ownership, dependencies, and reversibility before removal. The useful output is a CI runner label cleanup pull request with label references, runner inventory, queue evidence, replacement label, and rollback note: Remap jobs to the new runner label before deleting the old label, then make the final decision easy to audit later.

Key takeaways

• Review stale CI runner labels and workflow routing rules through Label references, Runner inventory, Queue behavior, not age alone.
• Use one full CI cycle across default, release, scheduled, and manually triggered workflows before deciding that quiet means unused.
• Start with the reversible move: remap jobs to the new runner label before deleting the old label.
• Slow down when stranding jobs or preserving expensive runner capacity nobody still needs is still plausible.
• Prevent repeat cleanup by making teams create runner labels with owner, capability, fleet source, and retirement trigger.

Map Runner Routing

Start with one CI fleet across runner labels, workflow matrices, queued jobs, self-hosted runner groups, hardware capabilities, and branch filters. 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.

Runner Label Evidence

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 CI runner label cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Label references	Workflow YAML, reusable jobs, matrix includes, scripts, and documentation	No supported workflow requests the old label
Runner inventory	Online runners, groups, OS, architecture, hardware devices, network zone, and concurrency	The label points to missing or replaced capacity
Queue behavior	Pending jobs, skipped jobs, retry patterns, and branch-specific failures	Removing or remapping the label will not strand jobs
Capability replacement	New label, hosted runner option, container image, or hardware pool	Jobs have a clear current target

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 Label Reference Check

Search workflow routing before deleting or renaming self-hosted runner labels.

rg "runs-on:|labels:|self-hosted|runner" .github .gitlab ci
rg "gpu|arm64|macos|privileged|deploy-runner" .github .gitlab ci docs
rg "workflow_call|matrix:|include:" .github/workflows

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.

Remap Jobs Before Removing Labels

Use the least permanent move that proves the decision. In CI runner label 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.

• Remap jobs to the new runner label before deleting the old label.
• Remove one label family from matrices and reusable workflows at a time.
• Watch queued and skipped jobs across branches before retiring runner groups.

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.

Builds With Special Hardware

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

• Release signing, mobile builds, GPU tests, privileged Docker builds, and private-network deploys.
• Reusable workflows consumed by repositories outside the obvious codebase.
• Long-lived release branches with their own runner filters.

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 Runner Label Cleanup

Run CI runner label cleanup as a decision review, not an open-ended hygiene project.

1. Pick the narrow scope and export the candidate list.
2. Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
3. Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
4. Apply the least permanent useful change first.
5. Watch the signals that would reveal a bad decision.
6. Complete the final removal only after the review window closes.
7. Save a CI runner label cleanup pull request with label references, runner inventory, queue evidence, replacement label, and rollback note.

For broader cleanup planning, use the cleanup library to pair this guide with related notes.

Generate Labels From a Catalog

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

• Create runner labels with owner, capability, fleet source, and retirement trigger.
• Keep workflow labels generated from a small approved runner catalog.
• Review labels whenever hardware, network access, or self-hosted runner groups change.

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 runner labels and workflow routing rules in CI pipelines, self-hosted runners, reusable workflows, release branches, artifact builds, and platform ownership records
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Label references, Runner inventory, and owner confirmation
First reversible move	Remap jobs to the new runner label before deleting the old label
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 full CI cycle across default, release, scheduled, and manually triggered workflows
Prevention rule	Create runner labels with owner, capability, fleet source, and retirement 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 CI runner label cleanup?

Use one full CI cycle across default, release, scheduled, and manually triggered workflows 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, remap jobs to the new runner label before deleting the old label. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to release signing, mobile builds, gpu tests, privileged docker builds, and private-network deploys. 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.