analyze-regression

Name

ci:analyze-regression

Synopsis

/ci:analyze-regression <regression id>

Description

The ci:analyze-regression command analyzes details for a specific Component Readiness regression and suggests next steps for investigation.

The command performs a full analysis regardless of whether the regression has been triaged. For triaged regressions, it also fetches the linked JIRA issue to analyze whether someone is actively working on the fix or if the issue needs attention.

This command is useful for:

• Understanding regression patterns and failure modes
• Checking if a triaged regression is being actively worked on or needs attention
• Identifying related regressions that might be caused by the same issue
• Getting pointers on where to investigate next

Implementation

Important: Avoiding user permission prompts when running scripts

When calling Python skill scripts via the Bash tool, always run the script directly without piping the output through inline Python (python3 -c "..."). Complex piped commands trigger user permission prompts, while simple python3 script.py args calls are auto-approved.

• Do: python3 script.py args --format json 2>/dev/null — run the script directly and process the JSON output in your reasoning
• Don't: python3 script.py args | python3 -c "import json; ..." — piped inline Python triggers permission prompts

Parse and analyze the JSON output from scripts using your own reasoning capabilities rather than shell pipelines.

Obtaining the DPCR authentication token from mounted kubeconfig

The triage and bug filing steps (step 14) require a Bearer token from the DPCR cluster (api.cr.j7t7.p1.openshiftapps.com:6443). When running in a container with ~/.kube mounted (read-only), the token is extracted directly from the mounted kubeconfig using oc:

# Find the oc context for the DPCR cluster from the mounted kubeconfig
DPCR_CONTEXT=$(oc config get-contexts -o name 2>/dev/null | while read -r ctx; do
  server=$(oc config view -o jsonpath="{.clusters[?(@.name=='$(oc config view -o jsonpath="{.contexts[?(@.name=='$ctx')].context.cluster}" 2>/dev/null)')].cluster.server}" 2>/dev/null || echo "")
  server_clean=$(echo "$server" | sed -E 's|^https?://||')
  if [ "$server_clean" = "api.cr.j7t7.p1.openshiftapps.com:6443" ]; then
    echo "$ctx"
    break
  fi
done)

# Extract the token from the DPCR context
if [ -z "$DPCR_CONTEXT" ]; then
  echo "ERROR: Could not find a DPCR cluster context in kubeconfig. Set DPCR_CONTEXT manually or run: oc login https://api.cr.j7t7.p1.openshiftapps.com:6443"
  exit 1
fi
TOKEN=$(oc whoami -t --context="$DPCR_CONTEXT" 2>/dev/null)