I have a multi-module QA project that I need to check out and build. I want the build step to not run any tests except for certain ones in a specific sub-module.
If I attempt to list the test classes as part of the main build, it doesn't seem to find the tests or it fails because it tries running tests in other other modules. I then tried separating the build step from the test step. I added a Pre-build step using "Invoke top-level Maven targets", but it seems that it uses a "private" maven repository, so when I attempt to run tests as part of the main Maven build command, it can't find the pre-built modules because it is looking in a different repository. It is unclear which "private" maven repository is being used as it doesn't give an option like the main maven build step does when selecting which private repo to use. There is an option to NOT use a private repository, but it doesn't seem to actually work and ALWAYS uses a private repository. If I try to uncheck the box to "Use Private Repository", it won't stick. If I try to just run it all as a shell, it won't use the maven settings file as defined in the job, though I could probably hard code it. Id rather not do that. Is there a better way I'm missing or how do I specify in one command to run tests in a specific module and skip all other modules? Thanks! -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPJK9%3DJ2hgDE%3Dv-7QsVsFzFnaKXY5uUbfa86xoSO-eFR4MJ0-g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
