Import the JUnit XML that eclipseTest writes - #5
Merged
Merged
Conversation
TeamCity shows no test names for eclipseTest. A failed run is just a bare Gradle exception in the UI. eclipseTest is not a Gradle Test task, so the Gradle runner's own test listener never sees it. From eclipse-buildship#1375 on it writes JUnit XML again, so pick that up with the XML report processing feature. The rules are narrow on purpose. A wildcard over test-results would also match what a real Test task produces, and the runner already reports those, so every such test would show up twice. The sanity check runs no tests and is left out, so that "no reports found" in a build log always means something went wrong.
donat
force-pushed
the
donat/ci/import-eclipsetest-junit-xml
branch
from
September 8, 2026 13:13
6a37c68 to
f1c5234
Compare
donat
marked this pull request as ready for review
September 8, 2026 13:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The TeamCity side of eclipse-buildship#1375. Merge that one first, this does nothing on its own.
eclipseTestis not a GradleTesttask, so the Gradle runner's own test listener never sees it and TeamCity shows no test names. A failed run is just a bare Gradle exception in the UI. The Buildship PR makes the task write JUnit XML again, this picks it up with the XML report processing feature.The rules are narrow on purpose:
A wildcard over
test-resultswould also match what a realTesttask produces, and the Gradle runner already reports those, so every such test would show up twice. The single*matters too, the binary results now live in abinarysubdirectory next to the XML files.The sanity check scenario runs no tests, so it does not get the feature. That way "no reports found" in a build log always means something went wrong rather than being expected noise on every phase 1 build.
Verified with
mvn teamcity-configs:generateon Java 21: 51 of the 52 individual scenario build types get thexml-report-pluginextension, the sanity check is the one that does not.