With you pom configuration, Jenkins should mark your build as unstable.
I now that maven job used to detect soapui junit xml files but this was prior the groupId/artifactId of the plugin changed. Maybe this does not work anymore.
You can also use a freestyle job which allows you to configure the directory where the junit xml files are generated (configure post-build step "Publish JUnit test result report")
I have started a summary about this here:
https://github.com/redfish4ktc/maven-so ... ps#jenkinsSome remarks about the plugin configuration in your pom (not related to jenkins failures/errors detection)
* use exportAll instead of exportwAll
* as most of the configuration for both executions is the same, you can put it outside of the executions block
<plugin>
<groupId>com.smartbear.soapui</groupId>
<artifactId>soapui-maven-plugin</artifactId>
<version>4.6.1</version>
<configuration>
<junitReport>true</junitReport>
<exportAll>true</exportAll>
<outputFolder>target/surefire-reports</outputFolder>
<printReport>true</printReport>
<testFailIgnore>true</testFailIgnore>
</configuration>
<executions>
<execution>
<id>run-soap-test-1</id>
<configuration>
<projectFile>xxx.xml</projectFile>
<testSuite>xxxSuite</testSuite>
</configuration>
<goals>
<goal>test</goal>
</goals>
<phase>test</phase>
</execution>
<execution>
<id>run-soap-test-2</id>
<configuration>
<projectFile>xxx.xml</projectFile>
<testSuite>xxxSuite</testSuite>
</configuration>
<goals>
<goal>test</goal>
</goals>
<phase>test</phase>
</execution>
</executions>
</plugin>