Hi Nate,
there are several things you can do with maven:
1. I'm wondering whether you'll always execute pitest in your
build. I usually configure pitest to be executed by activating a
profile or by running the pitest goal explicitly. Usually I don't
want to execute pitest on each and every "mvn clean install". If
you omit the pitest goal pitest won't run.
2. You can define a maven property for the skip option (in your parent pom) and overwrite it's value in your jenkins job:
<properties>
<pitest.excection.skip>false</pitest.execution.skip> <!-- dont skip when property ommited -->
</properties>
.....
<build>
....
<groupId>org.pitest</groupId>
<artifactId>pitest-maven</artifactId>
<configuration>
<skip>${pitest.exection.skip}</skip>
......
</configuration>
......
</build>
If you call your jenkins job with -Dpitest.exection.skip=true execution should be skipped.
I hope that helps,
Regards
Stefan
--
You received this message because you are subscribed to the Google Groups "PIT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pitusers+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "PIT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pitusers/DSNPG9OQRf8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pitusers+u...@googlegroups.com.