
Buildtime
io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026
构建瓶颈分析器:最慢步骤、运行趋势以及跨 CI 运行的缓存相关性。
AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。
原文描述
Build bottleneck profiler: slowest steps, run trend, and cache correlation across CI runs.
概览
Buildtime 的本地 MCP 服务;无需登录;STDIO。
暂无 AI 概览:以下信息来自注册中心条目和服务本身。
安装
在 SourceWeft 中
- 打开 控制台中的 Buildtime,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
buildtime
Your builds keep getting slower, but which step is to blame? buildtime profiles a set of CI runs — per-step durations and, where known, cache hits — and answers with the numbers that point at the bottleneck:
- Per-step statistics — for every distinct step name: how many runs contained it, its total, average, and maximum duration, and its share of the grand total, sorted slowest first (ties by name)
- Slowest step — the first entry in that ranking
- Trend — the runs, in the order supplied, split into a
first half and a second half (the middle run of an odd count
belongs to the first half), with each half's average run
total and the percentage delta between them;
nullwith fewer than two runs, and the delta itself isnullwhen the first half averages zero - Cache correlation — a run counts as "with cache" when at
least one of its steps reports a cache hit; buildtime
reports both group sizes and each group's average run total
(
nullfor an empty group, never zero-filled) - Flagged slowest — when you pass a slow threshold, the steps whose average duration meets or exceeds it, in slowest-first order
All floats are rounded to four decimal places. The computation is pure and local: no network, no configuration, no files read beyond the runs you pass in. Invalid input — a missing run, a step without a duration, a negative duration — is rejected with an error naming the offending path, and no partial profile is produced.
CLI
runs.json contains the full arguments object:
conclusion and cache_hit are optional per run / per step,
and slow_threshold_seconds is optional overall. The profile
is printed as JSON.
Exit codes: 0 on success, 1 on a runtime error (including
an unreadable or invalid runs file, or invalid input), 2
on a usage error.
MCP server
MCP client config:
Tools
-
analyze_build_times— Profile build bottlenecks across CI runs.runs(array, required, at least one) — runs as{run_id, conclusion?, steps}objects, where each step is{name, duration_seconds, cache_hit?}slow_threshold_seconds(number, optional, >= 0) — flag steps whose average duration meets this threshold
Returns
{run_count, grand_total_seconds, step_stats, slowest_step, trend, cache, flagged_slowest}.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
来源:README.md,提交 c4139dc
工具
0版本历史
1- v0.1.0最新Nov 3, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分