Clojurians Log v2
announcements 2026-09-22
The test results tab in Jenkins CI/CD used to be the part of my build I trusted least, mostly because of mangled stack traces, nonsensical durations, and random failures. It turns out the issue was the bad XML being fed into Jenkins rather than the tool itself. To solve it, I put together a plugin that produces clean XML I can actually rely on.
https://github.com/robinlahtinen/lein-junit-xml v0.1.0 is out — a Leiningen plugin that writes JUnit-compliant XML reports from test results.
Highlights:
- Non-invasive: delegates to lein test, so selectors, exit codes and lein retest keep working.
- Honest totals: selector-excluded tests are reported as skipped, never dropped.
- Verified: against JUnit's own report schema and the Jenkins JUnit parser.
Add the plugin to :plugins in project.clj:
:plugins [[com.github.robinlahtinen/lein-junit-xml "0.1.0"]]lein junit-xml!
ooo i forgot about junit
I thought clojure.test was supposed to be generate jUnit XML output directly? https://clojuredocs.org/clojure.test.junit Are there bugs in that which should be fixed?
Yeah, unfortunately clojure.test.junit has a few design issues that aren't easily patchable: it dumps to stdout instead of files, breaks lein retest by overriding the reporter, and outputs schema-invalid XML that may show as broken on CI.
Thanks. I suspected it had some rough edges but didn't realize it was that broken.
figure out yesterday but did you just give up on all that or do you want to still try to do something he dad said you’re going to yell at him so he’s worried thanks okay so it’s that you’re not seeing it as a crisis so we need to still do something or