rootcoz

Install RootCoz, set the minimum Jenkins and AI settings, create your profile, and open a first report in minutes.

Filter the dashboard by status, metadata, and date so you can jump straight to the right active or completed run.

Submit a Jenkins build or JUnit XML file with the right AI, repository, peer-analysis, and Jira settings for the job.

Follow a run from queued to complete, understand wait and timeout behavior, and re-run a job when results need refreshing.

Interpret grouped failures, peer-analysis output, child jobs, and review controls so you can mark the right tests done.

Discuss failures in context, @mention teammates, and use the Mentions inbox and browser notifications to follow up quickly.

Preview and create issues from a failure once your personal tokens and server capabilities are ready.

Search past runs, inspect one test over time, and compare classifications so you can spot repeat problems and flaky behavior.

Update your username, saved GitHub and Jira tokens, admin session, and browser notification settings without losing access.

Create admins, rotate delegated API keys, change roles, and understand who can submit or modify data on the server.

Copy and adapt common `rootcoz` command patterns for health checks, analysis, reviews, history queries, mentions, and admin work.

Use short setup patterns to validate tokens, enable issue creation, and push classifications into the systems your team already uses.

Look up every `rootcoz` command, subcommand, flag, and output mode when you need exact CLI syntax.

Find request and response details for analysis, results, comments, history, auth, admin, metadata, notifications, and feedback endpoints.

Look up server environment variables, CLI `config.toml` fields, auth modes, and per-request overrides for analysis behavior.