microshift-ci:test-job

To analyze a MicroShift Prow CI job, provide the Prow job URL to fetch started and finished metadata, extract the MicroShift version from build logs, and aggregate per-scenario test outcomes into a structured report.

You can find the exact MicroShift version by parsing the job configuration and extracting the build version from the CI logs using a helper script, which then aggregates this data into a comprehensive Markdown report.

The best way to triage scenario failures is to enumerate test scenarios and aggregate per-scenario results, including failure details and artifact links, across different architectures and image types into a single JSON and Markdown report.

Yes, you can use a specific job ID as input to fetch Prow and GCS job metadata, parse job configuration, and generate a readable report with status, timing, architecture, and image type details.

To collect GCS artifact and log links, the analysis process fetches job execution intelligence and iterates through test scenarios, returning both JSON and Markdown formats with direct links to relevant artifacts.

Yes, this CI log triage process works for validating coverage before releases by providing engineers with job execution intelligence and scenario-by-scenario analysis to quickly collect evidence for release candidate decisions.