investigate-ci

Investigating GitHub Actions CI failures involves downloading workflow logs and test artifacts to pinpoint errors. This tool detects Maven or Gradle builds, extracts Gradle build-scan URLs, and summarizes test failures grouped by job or module for actionable remediation.

Yes, extracting Gradle build-scan URLs from CI logs is supported. By providing a PR number or GitHub Actions URL, the tool downloads workflow logs, detects Gradle as the build tool, and extracts available build-scan URLs for deep failure analysis.

Yes, this tool works with both Maven and Gradle. It automatically detects the target build tool for the branch being tested to enable correct parsing of Maven Surefire and Gradle test outputs, grouping failures by job or module.

The best way to group test failures from Maven Surefire outputs is to use an automated CI investigation tool. It downloads logs and artifacts, detects Maven, and summarizes Surefire test failures grouped by job and module with root-cause hypotheses.

To get actionable next steps to fix failing CI pipelines, provide a PR number or GitHub Actions URL. The tool analyzes downloaded logs and test reports, extracts failures, and provides a concise summary with recommendations to resolve the build issues.

Downloading test-report artifacts is needed for CI failure analysis to enable deep investigation beyond standard logs. Artifacts contain detailed Maven Surefire or Gradle test outputs required to accurately extract failures and suggest root-cause hypotheses.