Branch: refs/heads/reduce-postbuild-echo-steps Home: https://github.com/xwiki/xwiki-jenkins-pipeline Commit: 2098be6ecea1a80108711fb8f898d1931fbc5d99 https://github.com/xwiki/xwiki-jenkins-pipeline/commit/2098be6ecea1a80108711... Author: Michael Hamann <[email protected]> Date: 2026-06-30 (Tue, 30 Jun 2026) Changed paths: M vars/xwikiBuild.groovy Log Message: ----------- [Misc] Batch post-build diagnostic logging to reduce pipeline step overhead Each echoXWiki call is a pipeline "echo" step that gets persisted to the build's flow graph, costing in the order of a second per step. Since getFailingTests() can return a hundred or more failing tests, the per-test logging in the screenshot-attaching and flicker-detection post-build passes added hundreds of echo steps, making each pass take several minutes (~9 minutes was observed for the screenshot pass alone after the directory listing cache had already removed the remote round-trips). Accumulate the per-test diagnostics in plain lists (assigning to a local variable is not a pipeline step) and emit them with a single echoXWiki call at the end of each pass instead of one or several lines per test. Also drop the per-candidate-directory "No matching screenshot found" line (redundant with the per-test summary) and leftover DEBUG lines in the flicker loop. 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