This message was deleted.
# develocity
s
This message was deleted.
t
you might try wiring it up via the built in registration helper?
ImportJUnitXmlReports.register(tasks, tasks.named("nameOfYourOsgiTestTask"), GENERIC)
it will hook it up as a finalizer and is also aware of caching etc so that it only runs when the test task runs.
If a test Fails in Jenkins this custom task sends it to Gradle Ent as having passed not failed.
AFAIK It just parses the xml so that would tell me your xml outputs are lying to you?
m
Could you please share an XML file of a failing test? Maybe the format is not fully supported?
r
hey @Marc Philipp sorry about delay returning to this here is an example of a failing test XML which is causing issues, this test failed as seen in XML but on Gradle ent is passed (screenshot) . Code is open source so i can share example, test in Q is here , a gradle convention plugin here provides the task to ingest to gradle ent , any advise appreciated
m
Thanks! It seems
<error>
elements within a
<testcase>
are currently not handled, only
<failure>
ones.
I’ll see to it that we enhance this in the next patch release of the Gradle Enterprise plugin.
r
Thanks Marc, that would be much appreciated.
d
Hello @Ronanb Browne We just released the Gradle Enterprise Gradle plugin v3.12.2, which now also supports the
<error>
element.
🙌 2
r
Thanks folks we will test and get back to you