microshift-ci:continue-session

You can resume MicroShift CI debugging by providing a completed prow job URL to automatically download CI Doctor artifacts and set up a local work directory. This prepares per-job reports, summaries, and bug mappings for continued investigation without re-running the entire pipeline.

Downloading CI Doctor artifacts requires converting the prow job URL to a GCS path, then using gsutil to fetch started.json and derive the workdir date. The process uses jq to produce a JSON summary of downloaded releases and report availability.

Yes, you need gsutil and jq installed locally to continue Prow CI troubleshooting. gsutil handles downloading artifacts from the GCS path, while jq parses JSON data to generate a summary of downloaded releases and report availability.

Yes, you can re-run aggregation and finalization steps for MicroShift nightly CI results. The downloaded artifacts create a correctly structured local workdir that enables re-running subsequent bug-creation steps using the same layout as the doctor workflow.

The best way to inspect Jira bugs mapped from MicroShift CI failures is to resume the CI Doctor session locally. This pulls per-job reports, summaries, and bug mappings into a local workdir for immediate review without re-running the entire pipeline.