explainError: Explain Error with AI

• collectDownstreamLogs : boolean (optional)
  Include logs from failed downstream jobs triggered by this build.
  
  Downstream discovery is disabled by default to avoid expensive scans on large Jenkins controllers. Enable this only when you want the AI analysis to include sub-job failures.
  
  When enabled, use Downstream Job Pattern to restrict which downstream jobs are collected.
• customContext : String (optional)
• downstreamJobPattern : String (optional)
  Regular expression matched against downstream job full names.
  
  This field is used only when Collect Downstream Logs is enabled. Jobs that do not match the pattern are skipped.
  
  Examples:

  • team-folder/.*/deploy-.* matches nested deploy jobs inside team-folder
  • release-pipeline|hotfix-pipeline matches either job name exactly
  • .* matches all downstream jobs (use with caution)

  Leave empty to collect no downstream jobs.
• language : String (optional)
  Preferred language for the AI response. Examples: English, Français, Deutsch, 中文, 日本語, Español. Leave empty to default to English.
• logPattern : String (optional)
  Regular expression pattern to match error lines in the build log. For example:

  • ERROR|error|Error - matches lines containing any form of "error"
  • FAILED|failed|Failed - matches lines containing any form of "failed"
  • Exception|exception - matches lines containing exceptions

  Leave empty to analyze all lines in the build log.
• maxLines : int (optional)
  Maximum number of lines to analyze from the build log. This helps to:

  • Limit API costs by not sending huge logs to the AI service
  • Focus analysis on the most recent/relevant errors
  • Improve response times

  
  Default: 100 lines
  Set to 0: Analyze unlimited lines (use with caution for large logs)