Branch: refs/heads/display-maven-command-for-failing-tests Home: https://github.com/xwiki/xwiki-jenkins-pipeline Commit: 4b415b29b66edb1831cecc357acd3eded5ba8e59 https://github.com/xwiki/xwiki-jenkins-pipeline/commit/4b415b29b66edb1831cec... Author: Michael Hamann <[email protected]> Date: 2026-06-30 (Tue, 30 Jun 2026) Changed paths: M vars/xwikiBuild.groovy Log Message: ----------- [Misc] Display the Maven command used for each failing test Tests are executed in several separate, parallel Maven builds (the main, quality, docker and IT configurations all funnel through xwikiBuild() with a different name). When a test fails it was not possible to tell, from the test result page, which exact Maven command produced the failure. Attach the exact Maven command to each failing test's description, in the same area as the Develocity (GE) links. Because getFailingTests() returns the failing tests for the whole job (JENKINS-49339) while the builds run in parallel, the command is build-specific and must be attributed to the right build: a test belongs to this build when its JUnit report directory exists in this build's workspace on this agent (filterTestsExecutedByThisBuild()), which is race-free since each build reads only its own filesystem. Per-configuration and main-vs-quality failures are distinct test entries living in distinct workspaces, so each entry is correctly labeled with its own build's command. Reuse the same filter to scope the per-test work to this build's own tests: - screenshot attachment now skips tests run by other parallel builds, - flicker marking now writes descriptions only for this build's own tests, - the whole post-build test processing (including the costly Jira flicker lookup) is skipped when this build ran none of the failing tests. The aggregate decisions (flicker summary, "only flickers?" result and the resulting email/notification) keep their whole-job meaning, so notification behaviour is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-jenkins-pipeline/settings/notifications