Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-jenkins-pipeline Commit: 3af132aa961b0cbca889298519d87d5849654d33 https://github.com/xwiki/xwiki-jenkins-pipeline/commit/3af132aa961b0cbca8892... Author: Michael Hamann <[email protected]> Date: 2026-07-29 (Wed, 29 Jul 2026) Changed paths: M src/test/java/org/xwiki/jenkins/pipeline/XWikiBuildTest.java M vars/xwikiBuild.groovy Log Message: ----------- [Misc] Link archived screenshots and videos in failing test descriptions * Point the description of a failing test to the screenshot archived as a build artifact instead of embedding its content as a "data:" URI. The "Safe HTML" description syntax (OWASP Markup Formatter plugin) only allows the http(s) protocols in "src" and "href" attributes, so it removed the "data:" URIs and then the <img>/<a> tags that had become attribute-less, leaving a "Screenshot" title with no image below it. This also keeps the descriptions (and thus the build's junitResult.xml in which they are saved) small since a base64-encoded screenshot used to be inlined twice per failing test. * Link the video of the failing test when there's one. Contrary to the screenshot it's only linked and never embedded since browsers cannot play these Flash videos. * Also look for the screenshots and videos in "<maven.build.dir>/<configuration>/screenshots", where the docker-based test framework saved them before XWIKI-24536 moved them directly under the Maven build directory. They are archived but were never found for the projects depending on an older version of the test framework, which is the case of the contrib extensions built against an older platform version (e.g. application-changerequest). * Copy the screenshots saved outside the workspace into the test's target directory and archive them, so that they can be linked too. This is the case of the screenshots of the legacy (non-docker) test framework, which saves them in the temporary directory when the "screenshotDirectory" system property is not set, i.e. when the build activates the "docker" Maven profile (e.g. application-replication). * Search all the possible screenshot locations with a single listing per directory, which keeps the number of remote round-trips to the build agent lower than before. * Use "word-wrap" rather than "word-break" for the Maven command block since the latter is not part of the CSS properties allowed by the "Safe HTML" syntax, which silently dropped it. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-jenkins-pipeline/settings/notifications