The standard ‘buildPlugin()’ Jenkinsfile directive appears to capture Surefire test reports, but not Failsafe test reports. This means that failing integration tests in my plugin are (a) unreported and (b) don’t break the build. This might be happening to other plugins too.
The line of code in question is probably this: https://github.com/jenkins-infra/pipeline-library/blob/66a14842e350bd5364a1a70ca4287535cacc0390/vars/buildPlugin.groovy#L118 I’ve worked around it by saving the Failsafe reports to the Surefire directory but this is extremely fragile: if I have an integration test class with the same name and package as a unit test class (which could happen if integration tests are stored in a different test source directory), then the report for one could overwrite the other. Could someone confirm whether this is indeed a limitation in the current buildPlugin.groovy script or whether there is a different (robust) way to pick up Failsafe reports on ci.jenkins.io? Regards Chris -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/448e67fa-aef8-48bd-9ce7-cdbf7a7d5b7f%40www.fastmail.com. For more options, visit https://groups.google.com/d/optout.
