Jenkins Configuration
Jenkins connection settings. The service is tied to a single Jenkins instance viaJENKINS_URL.
Jenkins server URL. The service connects to this Jenkins instance for all analysis requests.
Jenkins username for authentication.
Jenkins password or API token. Using an API token is recommended for security.
Enable SSL certificate verification. Set to
false for self-signed certificates.AI Provider Configuration
AI provider to use for analysis. Must be one of:
claude, gemini, or cursor.AI model identifier for the selected provider.
Model names vary by provider. Refer to your AI provider’s documentation for available models.
Timeout for AI CLI calls in minutes. Increase for slower models.
Must be greater than 0. Invalid values default to 10 minutes.
Claude CLI Configuration
Claude CLI supports two authentication methods:Direct API key authentication (simplest method).
Enable Vertex AI authentication for Claude.
Vertex AI region.
Google Cloud project ID for Vertex AI.
Gemini CLI Configuration
API key for Gemini CLI authentication.
Alternatively, use OAuth by running
gemini auth login. No environment variable needed for OAuth.Cursor Agent CLI Configuration
API key for Cursor Agent CLI authentication.
For web-based authentication in Docker, run:
docker exec <container-name> agent loginApplication Configuration
Log verbosity level. Options:
DEBUG, INFO, WARNING, ERROR.DEBUG- Detailed operation logsINFO- Milestones and important eventsWARNING- Warnings onlyERROR- Errors only
Enable debug mode with hot reload for development.
Generate HTML reports for analysis results.
When enabled, self-contained dark-themed HTML reports are generated alongside JSON results.
Optional Defaults
These settings provide default values that can be overridden per-request in API payloads.Default tests repository URL for cloning context.
Can be overridden via
tests_repo_url in the request payload.Default callback webhook URL for async analysis results.
Can be overridden via
callback_url in the request payload.Default callback headers as JSON string.
Can be overridden via
callback_headers in the request payload.Custom Prompt Configuration
Path to custom analysis prompt file for AI behavior customization.Mount your custom prompt file to this path to customize AI analysis behavior. See Custom Prompts for details.
Jira Integration (Optional)
Jira integration is completely optional. When configured, the service searches Jira for existing bugs matching PRODUCT BUG failures.Jira instance URL (Cloud or Server/DC). Setting this enables Jira integration.
Explicitly enable or disable Jira integration (overrides auto-detection).
When omitted, Jira is automatically enabled if
JIRA_URL and credentials are configured.Jira Cloud Authentication
Email address for Jira Cloud authentication.
Required for Jira Cloud. Use with
JIRA_API_TOKEN.API token for Jira Cloud authentication.
Generate API tokens from your Jira Cloud account settings.
Jira Server/DC Authentication
Personal Access Token for Jira Server/DC authentication.
Jira Search Configuration
Scope Jira searches to a specific project.
When omitted, searches across all projects accessible to the authenticated user.
SSL certificate verification for Jira connections.
Maximum number of Jira results per search.
Must be greater than 0. AI filters results for relevance after retrieval.
Per-Request Overrides
Most environment variables can be overridden in API request payloads. This allows different configurations per analysis without changing the server environment.See the Request Models for the complete list of request fields that override environment variables.
DEBUG- Server reload toggleLOG_LEVEL- Server log verbosityPROMPT_FILE- Server-local file path