jenkins-job-insight

Launch the service with the fastest supported setup, configure the minimum Jenkins and AI settings, register your profile, and inspect your first analysis from the CLI and web UI.

Queue a Jenkins build for analysis, choose per-run overrides, and understand how waiting, artifact downloads, and Jira enrichment affect the result.

Send raw failures or JUnit XML straight to the API and get structured analysis back when you want to work without a live Jenkins job.

Follow queued, waiting, running, failed, and completed jobs, then launch a re-analysis with adjusted settings when a run times out or needs another pass.

Use the report UI to inspect grouped failures, mark reviews complete, leave team comments, and override AI classifications when human judgment should win.

Set your display name, store GitHub and Jira credentials, validate them, and make issue creation work under your own identity instead of shared server credentials.

Search recurring failures, inspect a single test's trend over time, and use stored classifications and comments to spot flaky or systemic problems faster.

Preview generated issue content, pick the target repository or Jira project, edit the final text, and file follow-up work directly from an analysis report.

Give the AI better code context with test repositories, additional repositories, raw prompts, and artifact settings so the analysis can point to the right code and evidence.

Configure peer providers and models, tune debate rounds, and use multi-model review when you want higher-confidence triage for difficult failures.

Sync JJI classifications into matching Report Portal items, including child-job runs, and handle unmatched or partially successful pushes without losing track of what happened.

Create admin accounts, rotate keys, change roles, remove access, and use admin authentication safely from the UI, CLI, and API.

Look up every `jji` command, option, config-file interaction, and output mode when you need exact syntax.

Look up every endpoint, request field, query parameter, response shape, and status code for analysis, results, history, integrations, auth, and admin workflows.

Look up server environment variables, Docker Compose settings, `~/.config/jji/config.toml` fields, feature toggles, authentication knobs, and per-request override behavior.