coding agent · agent session
develocity MCP
Why did the most recent failed build fail? Brief diagnosis.
Agent
Asking broad first, then drilling into only the part that failed — not the raw log.
⏺ develocity · get_develocity_skill(build-and-test-troubleshooting)
└ guidance loaded
⏺ develocity · list_builds(outcome: failed)
└ igfdwy432t2zk · 1 summary row, not the 50KB log
⏺ develocity · get_build(igfdwy432t2zk, model: failures)
└ 3 test failures · drilled into failures only
3 test failures, all the same root cause: tests marked @PendingFeatureIf now pass unexpectedly on Maven 4.1.0-nightly. Spock treats an unexpected pass as a failure — the underlying feature was implemented, so the annotations need removing.
TestDistributionFailsafeExecutionFuncTest — supports redirectTestOutputToFile
TestDistributionSurefireExecutionFuncTest — supports redirectTestOutputToFile
TestDistributionRemoteExtensionFuncTest — captures test output
All in :build-agent-maven-test-distribution-test-func:testNightly_latest.
Build Scan: https://develocity.example.com/s/igfdwy432t2zk
› Ask about your builds▸