fetch-buildkite-logs
GitHub该技能用于获取并分析 Buildkite CI 构建日志。通过解析 URL 提取管道和构建号,验证 API 令牌后调用接口查询构建状态、失败作业及详细日志,去除 ANSI 码后总结失败原因并提供修复建议。
Trigger Scenarios
Install
npx skills add ray-project/ray --skill fetch-buildkite-logs -g -y
SKILL.md
Frontmatter
{
"name": "fetch-buildkite-logs",
"description": "Fetch and analyze Buildkite CI build logs for failures"
}
Fetch Buildkite Logs
Prerequisites
BUILDKITE_API_TOKENmust be set in the environment (typically~/.bashrc)- If not configured, direct user to
doc/source/ray-contribute/agent-development.mdfor setup
Parsing the Buildkite URL
A Buildkite URL has the form:
https://buildkite.com/ray-project/<PIPELINE>/builds/<BUILD_NUM>#<JOB_ID>
Always extract <PIPELINE> (e.g. premerge, postmerge) and <BUILD_NUM> from the URL the user provides. Do not hardcode premerge — the same skill is used for all pipelines. If a #<JOB_ID> fragment is present, it identifies a specific real job (not a group/wait job) and can be queried directly.
Steps
- Verify token:
echo $BUILDKITE_API_TOKEN | head -c4 - If token missing, stop and show setup instructions from the dev docs
- Fetch build (use the pipeline from the URL):
curl -s -H "Authorization: Bearer $BUILDKITE_API_TOKEN" \ "https://api.buildkite.com/v2/organizations/ray-project/pipelines/<PIPELINE>/builds/<BUILD_NUM>" - If a job ID is present in the URL fragment, look it up directly:
curl -s -H "Authorization: Bearer $BUILDKITE_API_TOKEN" \ "https://api.buildkite.com/v2/organizations/ray-project/pipelines/<PIPELINE>/builds/<BUILD_NUM>" \ | python3 -c "import sys,json; jobs=json.load(sys.stdin)['jobs']; [print(f\"{j['id']} {j.get('name')} -> {j.get('state')}\") for j in jobs if j['id']=='<JOB_ID>']" - Otherwise list failed/broken jobs:
curl -s -H "Authorization: Bearer $BUILDKITE_API_TOKEN" \ "https://api.buildkite.com/v2/organizations/ray-project/pipelines/<PIPELINE>/builds/<BUILD_NUM>" \ | python3 -c "import sys,json; jobs=json.load(sys.stdin)['jobs']; [print(f\"{j['id']} {j['name']} -> {j['state']}\") for j in jobs if j.get('state') in ('failed','broken')]" - Fetch individual job log:
Logs come back as JSON with acurl -s -H "Authorization: Bearer $BUILDKITE_API_TOKEN" \ "https://api.buildkite.com/v2/organizations/ray-project/pipelines/<PIPELINE>/builds/<BUILD_NUM>/jobs/<JOB_ID>/log" \ > /tmp/log_<JOB_ID>.jsoncontentfield containing ANSI escape codes — strip them withre.sub(r'\x1b\[[0-9;]*m', '', content)before grepping. - Summarize failures and suggest fixes.
Authentication note
If curl returns {"message":"No organization found"}, the configured token does not have access to ray-project. The user may have a separate org-scoped token — ask them which env var to source.
Version History
- 3fb63d9 Current 2026-07-25 11:18


