القائمة
Fetch Jenkins build failures and generate a context file for analysis
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Full pipeline — gather failures, analyze, and search for known fixes
Analyze a context file of test failures and produce a fix report
Compare two builds and report new vs recurring failures
Import a verified fix from a merged PR into the knowledge base
Search the knowledge base for known fixes related to test failures
استنادا إلى تصنيف SOC المهني
| name | gather-failures |
| description | Fetch Jenkins build failures and generate a context file for analysis |
| user-invocable | true |
Fetch test failure data from a Jenkins build, sync repo clones, resolve test and product code, and save a context file.
/gather-failures <job-path> --build <number> [--limit N] [--type TYPE]
<job-path> (required) — full Jenkins job path: <team>/<ipv4|ipv6>/<component> (e.g. proton/ipv4/sat-stream-rhel9-Insights-Advisor)--build <number> (required) — the Jenkins build number (e.g. --build 35)Examples:
/gather-failures proton/ipv4/sat-stream-rhel9-Insights-Advisor --build 35/gather-failures proton/ipv4/sat-stream-rhel9-RHCloud --build 1019/gather-failures proton/ipv4/sat-stream-rhel9-RHCloud --build 1019 --limit 5houston analyze "<job-path>" --build <number> --verbose 2>&1
Parse the job path and --build number from the user's arguments. If the user passes extra flags like --limit or --type, include them.
If houston fails, report the error and stop.
Houston will print the path to the context file (e.g. resources/analysis/<job>/<build>/context.md). Read the entire file. It may be large — use offset/limit parameters to read in chunks.
The context file contains:
Print a summary:
/analyze-failures