Branch: refs/heads/ci-check-develocity-read Home: https://github.com/xwiki/xwiki-dev-llm Commit: 1950b659694f1ebe36a2e6eaddc1e88a981be099 https://github.com/xwiki/xwiki-dev-llm/commit/1950b659694f1ebe36a2e6eaddc1e8... Author: Vincent Massol <[email protected]> Date: 2026-09-18 (Fri, 18 Sep 2026) Changed paths: M README.md M xwiki/okf/servers/jenkins.md M xwiki/skills/xwiki-ci-check/SKILL.md A xwiki/skills/xwiki-ci-check/tools/dv-test-history.mjs Log Message: ----------- [Misc] Analyse a failing CI test from Develocity, not from the build log * Add tools/dv-test-history.mjs, a wrapper around the dv-test-history analyser in xwiki/xwiki-dev-tools: it resolves a checkout (XWIKI_DEV_TOOLS, a sibling checkout, or a shallow clone in the plugin's state directory), passes the Develocity key the plugin already has under either of its two names, and prints only the report's header and key findings, the full report going to a file. * SKILL.md §3: a class 1 incident is analysed from that history rather than from the failing stage log, once per deep incident and never for class 2/3/4; the build scan links come from its --section block. * SKILL.md §3: the develocity MCP now serves a class 2 break whose stage log came back unclassified, class 1 having a better source. * okf/servers/jenkins.md: prefer dv-test-history over the develocity MCP for a flicker's history. * README.md: the skill entry, the XWIKI_DEV_TOOLS variable and the Develocity access section. 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-dev-llm/settings/notifications