I've also never heard of a way to do this.
But if this is worth pursuing, maybe we could script our way to a solution?
Say we build with no Junit tests as the first step of the job, then we run a script
that uses git to know which plugins were changed, and then call maven on each
relevant test plugin individually, letting only those JUnit tests run.
I think we would need to predefine a mapping to know which JUnit plugins should
be run based on which plugins were changed, but that should be possible.
If so, the script should be committed to our repo (and not be coded directly in
the Hudson job).
Just thinking out loud...
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [dschaefer@xxxxxxx]
Sent: February 19, 2015 2:40 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] gerrit verifier job timing
+1 from me too, but no, there isn’t a way to do that AFAIK.
Doug.
+1. There is also no need to run core tests if only UI plugins were modified.
-sergey