[OSS CI] Cost analysis & trim low-signal workflows
Open
@nil-is-all is already working on this.
Since May 30, 2026.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
Objective
Audit current ExecuTorch OSS CI spend, identify top cost drivers, and remove/consolidate redundant or low-value CI jobs.
Action Items
-
Review CI cost using the HUD cost analysis dashboard: https://hud.pytorch.org/cost_analysis?dateRange=7&granularity=day&groupby=workflow_name&chartType=stacked_bar&yAxis=cost&repos=pytorch%2Fexecutorch
-
Identify the top 5 most expensive workflows and evaluate ROI (signal value vs. cost)
-
Determine which workflows can be:
- Made conditional (only run on relevant file changes)
- Moved to nightly/periodic instead of per-PR
- Consolidated with other overlapping workflows
- Removed entirely (low/no signal)
-
Propose trimming plan with expected cost savings
Success Criteria
- Clear cost breakdown by workflow documented
- At least 2-3 workflows trimmed, consolidated, or moved to nightly
- Measurable reduction in CI cost per PR
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.