Aggregate LVMS periodic CI failures into an HTML summary report.
npx skills add https://github.com/openshift-eng/edge-tooling --skill lvms-ci-doctor
Please help me install this Agent Skill. Skill: lvms-ci:doctor Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/lvms-ci/skills/doctor Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill lvms-ci-doctor
LVMS release teams need fast, readable insight into why periodic CI jobs are failing, but manually correlating job failures across many releases and artifacts is time-consuming and error-prone.
Run /lvms-ci:doctor 4.20,4.21,main to analyze LVMS periodic CI failures for those releases and produce an HTML summary report.
High-intent search queries and answers about installing and using this skill.
To analyze LVMS CI failures across releases, aggregate periodic Prow job results into a single HTML report. Provide a comma-separated list of release versions to generate a timestamped, self-contained summary of per-job root causes.
Generating an HTML report for Prow periodic job failures requires deterministic artifact collection followed by LLM-based per-job analysis. This approach aggregates downloaded artifacts into a single actionable summary file for release engineering workflows.
Yes, you need gsutil, python3, and bash to perform deterministic CI artifact collection and aggregation. These dependencies fetch Prow job artifacts and execute the scripts required to prepare data for root cause analysis.
Yes, you can include the main branch alongside specific versions for failure analysis. Specify a comma-separated list like '4.20,4.21,main' to aggregate periodic CI job failures across all requested releases.
Per-job root cause analysis works by using deterministic scripts to fetch and prepare artifacts, then applying LLM agents only for the per-job analysis phase. This produces consistent, actionable writeups that are aggregated into a final HTML report.
The aggregated CI failure summary report saves as 'lvm-operator-ci-doctor-report.html' under a computed timestamped work directory. This deterministic output location ensures engineers can reliably locate the generated HTML summary file.
openshift-engDownload CI Doctor artifacts from a completed Prow job into a local workdir.
openshift-engAnalyze MicroShift CI failures across releases and rebase PRs into an HTML report.
vince-winkintelManage GitLab CI/CD pipelines, jobs, and artifacts.
openshift-engQuery Sippy's job/run/summary API to summarize Prow job failures by SIG.
