Skip to content

ci: surface surefire failures in backend workflow#26

Merged
vitorhugo-java merged 1 commit into
mainfrom
codex/fix-maven-test-execution-failure
May 25, 2026
Merged

ci: surface surefire failures in backend workflow#26
vitorhugo-java merged 1 commit into
mainfrom
codex/fix-maven-test-execution-failure

Conversation

@vitorhugo-java

Copy link
Copy Markdown
Owner

Motivation

  • Make test failures from the Maven Surefire plugin immediately diagnosable by printing a concise report summary into CI logs when tests fail.
  • Preserve full Surefire and JVM dump artifacts for post-failure analysis by uploading them as artifacts.
  • Reduce developer turnaround by surfacing failure details in the workflow so rerunning locally is less often required.

Description

  • Updated .github/workflows/backend.yml to add a failure-only step Print Surefire report summary on failure that prints the contents of files in target/surefire-reports (first 200 lines of *.txt) into the Action log.
  • Added a failure-only artifact upload step Upload Surefire reports using actions/upload-artifact@v4 to archive target/surefire-reports/** and JVM dump files (*.dump, *-jvmRun*.dump, *.dumpstream).
  • Left the existing packaged JAR upload step and normal build/test step (mvn -B -ntp clean verify) unchanged.

Testing

  • Verified the workflow YAML structure and the new steps by inspecting .github/workflows/backend.yml after the edit.
  • Ran mvn test -q in the local environment which failed due to external dependency resolution (org.springframework.boot:spring-boot-starter-parent:3.2.5 could not be fetched from Maven Central with HTTP 403), so end-to-end CI test execution could not be completed here.

Codex Task

@github-actions github-actions Bot added the ci/cd label May 25, 2026
@vitorhugo-java vitorhugo-java merged commit 322b4ee into main May 25, 2026
2 of 3 checks passed
@vitorhugo-java vitorhugo-java deleted the codex/fix-maven-test-execution-failure branch May 25, 2026 17:55
@github-actions

Copy link
Copy Markdown

Qodana for JVM

4 new problems were found

Inspection name Severity Problems
Nullability and data flow problems 🔶 Warning 2
Non-distinguishable logging calls ◽️ Notice 2
View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2025.3.2
        with:
          upload-result: true
Contact Qodana team

Contact us at qodana-support@jetbrains.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant