ci-cd

Diagnose CI/CD failures by retrieving complete job logs, locating error indicators, and correlating them with failed steps to identify root cause. This approach avoids guessing and applies to GitHub Actions and Screwdriver workflows using CLI tools like gh and sd-cmd.

Yes. GitHub Actions logs capture full step output and error context. Retrieve logs with the gh CLI, scan for failure points, and trace back to identify which step failed and why, enabling concrete fixes rather than speculation.

Use sd-cmd and Unix tools to fetch complete Screwdriver logs, search for error indicators and failed step markers, then correlate log sections with pipeline stages to pinpoint the exact failure and its cause.

Read logs end-to-end without assumptions: locate error messages, note the failing step, examine preceding context for cascading issues, and cross-reference against workflow configuration. Standard Unix commands help filter and correlate relevant log sections.

Yes. The gh CLI retrieves GitHub Actions logs efficiently, while sd-cmd accesses Screwdriver job logs. Both enable programmatic log analysis and error correlation necessary to move beyond speculation to concrete diagnosis.