29 lines
1.4 KiB
Markdown
29 lines
1.4 KiB
Markdown
# PR#137: The Code City Before the Mutation-CRAP Gate
|
|
|
|
> **WARNING:** This document describes only the change applied in this PR.
|
|
> It may already be outdated once the next PR is merged.
|
|
> Historic PR-documentation is not maintained along with new PRs — treat it as a snapshot, not as current documentation.
|
|
|
|
## Related Links
|
|
|
|
- [PR#133](2026-10-09-PR#133-werkcrappit-structure-views.md), werkcrappit 0.25.0 with the structure views
|
|
- [werkcrappit RFC 0003](https://git.javagil.de/mi/werkcrappit/src/branch/main/docs/rfcs/0003-structure-view.md), step 3: Werkator as the pilot
|
|
|
|
## The Problem
|
|
|
|
The nightly build `mutation` runs `pitest mutationCrapCheck mutationCrapCodeCharta`: the gate before the export.
|
|
When the gate fails, Gradle does not run the export, so the build has no code city and no structure views.
|
|
That happened on 2026-10-10: one mutant ended in a `MEMORY_ERROR`, the gate failed with an analysis error,
|
|
and `build/reports/codecharta/` stayed empty.
|
|
A failing gate is exactly when the code city helps most: it shows the methods to look at.
|
|
|
|
## Non-Goals
|
|
|
|
- No change of the limits, nor of the memory settings of PR#134 and PR#135.
|
|
|
|
## The Solution
|
|
|
|
- `.werkator.yml`: the build `mutation` runs `pitest mutationCrapCodeCharta mutationCrapCheck`, the export before the gate,
|
|
as werkcrappit's guide for hsadmin-ng does.
|
|
- Version 1.38.13: only the nightly build changes.
|