On Thu, Nov 12, 2015 at 8:50 PM, Mark Waite <[email protected]> wrote: > I tried -Dconcurrency=10 today and found no difference in wall clock time > compared to running without that argument. Does that argument depend on a > newer version of Jenkins
AFAIK this is available in 1.535+ parent POMs. Assuming you write `JenkinsRule` tests rather than unit tests, you should see ten tests start before any start to complete. Wall clock time is highly sensitive to your machine: number of processors, free RAM, HDD vs. SSD, etc. If you are patient you can try something like mvn clean test-compile; for c in 10 9 8 7 6 5 4 3 2 1; do echo "concurrency=$c"; time mvn surefire:test -Dconcurrency=$c -Dmaven.test.failure.ignore &>-; done -- 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/CANfRfr3aEOtZK%2B_M3Cxm%3DJ0gMt1Oc%3DWqP0GZp0YtqRQOJ1Eapw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
