September 2026 - notifications

[xwiki/xwiki-dev-llm] cee31a: [Misc] Find who caused a quality gate failure, and...
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/heads/ci-check-flicker-stabilisation Home: https://github.com/xwiki/xwiki-dev-llm Commit: cee31afb48c8fdf9e18f9985a3b68290460120dc https://github.com/xwiki/xwiki-dev-llm/commit/cee31afb48c8fdf9e18f9985a3b68… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M README.md M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs A xwiki/skills/xwiki-ci-check/tools/sonar-gate.mjs Log Message: ----------- [Misc] Find who caused a quality gate failure, and say so in the report * tools/sonar-gate.mjs reads the failing conditions of a branch's gate and the new-code issues under each — file, line, rule, severity, the day it was raised and the SCM author of the line — from SonarCloud, which is the only system that holds them: the Jenkins log says `QUALITY GATE STATUS: FAILED` and stops. * ci-check.mjs asks GitHub which commit last touched each of those files by the day the issue appeared, and puts conditions, issues and `culprits` in `sonar`. The rendered paste prints them under the incident. * Whose code, not who broke the build: a line's author is not a culprit, so this lands in `sonar.culprits`, never in `blame`, and no commit comment follows. Each name carries its provenance — Sonar's line author, or the commit's author only where Sonar had none. * Fails soft like the Develocity pass: no `SONARQUBE_TOKEN`, no gate facts, and `summary.sonar.unavailable` says so while the sweep is otherwise unchanged. * Measured on master: reliability of new code is C against a wanted A, on three issues — one BLOCKER NPE and two of one two-line change. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] b85d2d: [Misc] Name who caused a failing quality gate
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/heads/ci-check-flicker-stabilisation Home: https://github.com/xwiki/xwiki-dev-llm Commit: b85d2dabfd40f76a5fb634ef647d103c827ca10a https://github.com/xwiki/xwiki-dev-llm/commit/b85d2dabfd40f76a5fb634ef647d1… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Name who caused a failing quality gate * A gate failure is not authorless: SonarCloud carries the file, the line, the rule, the day it was raised and the SCM author of every new-code issue under the failing condition. §3 now sends the report there instead of declaring the failure unattributable, and `blame.reason` says where the author is. * Measured on master, 2026-09-19: `new_reliability_rating` fails on three issues, two of them one two-line change from one author. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 59b2f2: [Misc] Stabilise one proven flicker a run, and onl...
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/heads/ci-check-flicker-stabilisation Home: https://github.com/xwiki/xwiki-dev-llm Commit: 59b2f2361afa681b16ecb3fc378628a8081a9da0 https://github.com/xwiki/xwiki-dev-llm/commit/59b2f2361afa681b16ecb3fc37862… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M README.md M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/routine-prompt.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Stabilise one proven flicker a run, and only when nothing blocks a release * ci-check.mjs picks at most one stabilisation candidate per sweep — a proven, already-filed flicker that nothing answers, inside the horizon, not systematic, and the one among those that fails most often, since a fix can only be shown to work on a test a repeat run can catch failing. `summary.stabilise` carries it or the reason there is none, and the paste prints that reason as its own line. * The candidate keeps its evidence and its 28 days of Develocity whether or not it won a deep slot: a filed flicker sits low in the analysis budget by design, and the configuration breakdown is the first thing whoever fixes it reads. * Nothing is proposed while something release-blocking is open. A build break blocks at any age — a quality gate red for a fortnight is a fortnight of blocked releases — while a systematic test breakage stops blocking past the horizon, where the run may not write about it at all and so cannot work on it instead. * SKILL.md §5 gains the procedure: measure the rate on the configuration Develocity names, fix inside Tier C, measure again, and open one unassigned draft PR carrying both rates with their execution counts and what a clean series does not prove — or nothing at all when the second rate is no better. * A failing SonarCloud quality gate stops being `report, never fix`: it makes the build red for everyone, so it is the run's first fix, handed to xwiki-fix-sonarqube-issue and still under nobody's name. On a cycle-2 branch the gate itself is usually the bug, and turning it off there is a proposal to the team. * The digest names a stabilisation PR and is not withheld on the morning it opened one. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/tags/v1.12.12 Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 4f9f8a: [Misc] Release 1.12.12
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 4f9f8a93d6ac0ec8ebebfc49338178db9aebef5a https://github.com/xwiki/xwiki-dev-llm/commit/4f9f8a93d6ac0ec8ebebfc4933817… Author: github-actions[bot] <41898282+github-actions[bot](a)users.noreply.github.com> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json Log Message: ----------- [Misc] Release 1.12.12 * content edits only (no capability added or removed) To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/heads/ci-check-repeat-oracle Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] a3cf19: [Misc] Measure a flickering test's pass rate inste...
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: a3cf193afab1402effceb2398a32f6a960ec5c33 https://github.com/xwiki/xwiki-dev-llm/commit/a3cf193afab1402effceb2398a32f… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M README.md A xwiki/scripts/xwiki-it-repeat.mjs M xwiki/skills/xwiki-build/SKILL.md M xwiki/skills/xwiki-fix-flickering-docker-test/SKILL.md Log Message: ----------- [Misc] Measure a flickering test's pass rate instead of running it a few times * Add xwiki/scripts/xwiki-it-repeat.mjs, which runs one Docker functional test N times on one configuration and reports the pass rate, the failing repetitions' artifacts, a report.json and a summary.md a pull request can quote; --baseline prints the before/after comparison * Count test executions rather than Maven runs, and keep runs that died in beforeAll, hit the timeout or never got an IT slot out of the rate — a starved Docker daemon is a fact about the machine, not about the test * Provision the wiki once with xwiki.test.ui.keepRunning and repeat against it through the framework's external servlet engine (~70s per repetition rather than a full build); --mode fresh pays the full build and works with any servlet engine * Subtract the framework's "file outside target" failure about the keepRunning stop file, which is this tool's own footprint and not a result about the test, and write that file empty so the framework deletes it itself * Say what a clean series does not prove: zero failures in n executions bounds the failure rate below ~3/n, not at zero * Rewrite xwiki-fix-flickering-docker-test around measuring the rate before and after, dropping the `@RepeatedTest(failureThreshold = 1)` step that stops at the first failure; ask the developer before taking their machine for half an hour, and state that it needs no display so a routine can run it * Record that what blocks a release — compile breaks, poms, the quality gate — outranks flickers Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: 06aa6a40027560d5090a48512dd16cca99777f72 https://github.com/xwiki/xwiki-dev-llm/commit/06aa6a40027560d5090a48512dd16… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M xwiki/skills/xwiki-fix-flickering-docker-test/SKILL.md Log Message: ----------- [Misc] Keep the flickering-test skill about fixing a flickering test * Drop the release-priority paragraph and the "in a routine, launch without asking" clause: which red thing a scheduled sweep should spend its budget on is xwiki-ci-check's question, not one a developer fixing a named flicker ever asks * Cut the implementation rationale (why the external engine implies jetty_standalone) down to the constraint a caller acts on, and drop the framing that sold the tool rather than explaining it * Keep, tightened: why a rate rather than a pass, how to read a setup error, how many repetitions are worth running, reuse versus fresh, and the cost of taking a developer's machine Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> Commit: 703bde3c51fc42edfc507e2e5aa2f73c1ba0889a https://github.com/xwiki/xwiki-dev-llm/commit/703bde3c51fc42edfc507e2e5aa2f… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M README.md A xwiki/scripts/xwiki-it-repeat.mjs M xwiki/skills/xwiki-build/SKILL.md M xwiki/skills/xwiki-fix-flickering-docker-test/SKILL.md Log Message: ----------- Merge pull request #159 from xwiki/ci-check-repeat-oracle [Misc] Measure a flickering test's pass rate instead of running it a few times Compare: https://github.com/xwiki/xwiki-dev-llm/compare/56b7caac08ba...703bde3c51fc To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 06aa6a: [Misc] Keep the flickering-test skill about fixing...
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/heads/ci-check-repeat-oracle Home: https://github.com/xwiki/xwiki-dev-llm Commit: 06aa6a40027560d5090a48512dd16cca99777f72 https://github.com/xwiki/xwiki-dev-llm/commit/06aa6a40027560d5090a48512dd16… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M xwiki/skills/xwiki-fix-flickering-docker-test/SKILL.md Log Message: ----------- [Misc] Keep the flickering-test skill about fixing a flickering test * Drop the release-priority paragraph and the "in a routine, launch without asking" clause: which red thing a scheduled sweep should spend its budget on is xwiki-ci-check's question, not one a developer fixing a named flicker ever asks * Cut the implementation rationale (why the external engine implies jetty_standalone) down to the constraint a caller acts on, and drop the framing that sold the tool rather than explaining it * Keep, tightened: why a rate rather than a pass, how to read a setup error, how many repetitions are worth running, reuse versus fresh, and the cost of taking a developer's machine Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] a3cf19: [Misc] Measure a flickering test's pass rate inste...
by XWiki Notifications 19 Sep '26

19 Sep '26

Branch: refs/heads/ci-check-repeat-oracle Home: https://github.com/xwiki/xwiki-dev-llm Commit: a3cf193afab1402effceb2398a32f6a960ec5c33 https://github.com/xwiki/xwiki-dev-llm/commit/a3cf193afab1402effceb2398a32f… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M README.md A xwiki/scripts/xwiki-it-repeat.mjs M xwiki/skills/xwiki-build/SKILL.md M xwiki/skills/xwiki-fix-flickering-docker-test/SKILL.md Log Message: ----------- [Misc] Measure a flickering test's pass rate instead of running it a few times * Add xwiki/scripts/xwiki-it-repeat.mjs, which runs one Docker functional test N times on one configuration and reports the pass rate, the failing repetitions' artifacts, a report.json and a summary.md a pull request can quote; --baseline prints the before/after comparison * Count test executions rather than Maven runs, and keep runs that died in beforeAll, hit the timeout or never got an IT slot out of the rate — a starved Docker daemon is a fact about the machine, not about the test * Provision the wiki once with xwiki.test.ui.keepRunning and repeat against it through the framework's external servlet engine (~70s per repetition rather than a full build); --mode fresh pays the full build and works with any servlet engine * Subtract the framework's "file outside target" failure about the keepRunning stop file, which is this tool's own footprint and not a result about the test, and write that file empty so the framework deletes it itself * Say what a clean series does not prove: zero failures in n executions bounds the failure rate below ~3/n, not at zero * Rewrite xwiki-fix-flickering-docker-test around measuring the rate before and after, dropping the `@RepeatedTest(failureThreshold = 1)` step that stops at the first failure; ask the developer before taking their machine for half an hour, and state that it needs no display so a routine can run it * Record that what blocks a release — compile breaks, poms, the quality gate — outranks flickers Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki-contrib/xwiki-helm]
by XWiki Notifications 18 Sep '26

18 Sep '26

Branch: refs/heads/chore/enhance-tracking-activeinstalls Home: https://github.com/xwiki-contrib/xwiki-helm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki-contrib/xwiki-helm/settings/notifications

1 0