cicd-diagnostics

Name: cicd-diagnostics
Author: dotCMS

Diagnoses DotCMS GitHub Actions failures (PR builds, merge queue, nightly, trunk). Analyzes failed tests, root causes, compares runs. Use for "fails in GitHub", "merge queue failure", "PR build failed", "nightly build issue".

TL;DR

Diagnoses DotCMS CI/CD failures in GitHub Actions runs, PRs, merge queues, and nightly builds. Identifies root causes via log analysis, test pattern comparison, and failure pattern recognition.

What Is It

Diagnoses CI/CD failures in DotCMS GitHub Actions workflows
Analyzes test failures, merge queue issues, and PR build outcomes
Compares test results across PR, merge queue, and nightly runs
Identifies flaky tests and infrastructure issues

Key Features

CRITICAL - All scripts run from repository root, never use cd
CRITICAL - Python 3.8+ required; parameter order is strict
CRITICAL - RUN_ID always first, WORKSPACE always second in fetch-*.py
Use decision tree to guide investigation flow
Prioritize external issues before code changes
Compare PR and merge queue test results for discrepancies
Form hypotheses and validate with evidence
Always check for known issues and duplicates

How to Use

1.Identify what failed and gather evidence from logs
2.Run fetch-*.py scripts with correct parameter order: <RUN_ID> <WORKSPACE>
3.Use decision tree to determine failure type and next step
4.Check for external service issues first using external_issues.py
5.Compare PR and merge queue results for test filtering discrepancies
6.Present conclusions with confidence level and recommendations

Guardrails & Gotchas

CRITICAL - Never use cd to change directories
CRITICAL - Parameter order in fetch-*.py scripts must be RUN_ID first, WORKSPACE second
Don't use for local test execution or code logic debugging
Don't use for git operations unrelated to CI/CD
Don't run locally; always use GitHub Actions run URLs
Avoid running tests locally; use this skill only for CI/CD failures