> > How would that work with JTH tests as run via PCT, since these will only > pick up a Jenkins WAR from the local Maven repository > Actually they support other sources:
- JTH can take WAR from different sources, not only from local Maven repository (see WAR Exploder <https://github.com/jenkinsci/jenkins-test-harness/blob/master/src/main/java/org/jvnet/hudson/test/WarExploder.java#L71-L131>). I was a bit lazy during prototyping, so I was just putting WAR to war/target/jenkins - PCT supports "-war" option <https://github.com/jenkinsci/plugin-compat-tester#running-pct-manually>, which allows specifying a custom WAR path. I was using this a lot during JEP-200 testing in December/January. The new PCT Docker image also supports custom WAR specification Next week I will create a demo which actually runs JTH and PCT with a custom WAR file within the repository. BR, Oleg On Thursday, March 22, 2018 at 7:12:59 PM UTC+1, Jesse Glick wrote: > > On Thu, Mar 22, 2018 at 8:25 AM, Oleg Nenashev <[email protected] > <javascript:>> wrote: > > It allows the custom configuration to be transparently > > used with existing tests. > > How would that work with JTH tests as run via PCT, since these will > only pick up a Jenkins WAR from the local Maven repository? Do you > need to `mvn install:install-file` the custom WAR as a `SNAPSHOT` > version that can be fed to PCT? > -- 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/3a0d2bfd-e198-44b7-8ccb-837577bb8dc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
