Thanks for the response!
Hmm, haven't checked that yet, but i will do it as soon as I get back to it tomorrow (I'm in europe). What i can tell you is that i started the process via mvn test as a Jenkins build and spawned subthreads from this one.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/AWQtIDdFXYM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Thanks for the response!
Hmm, haven't checked that yet, but i will do it as soon as I get back to it tomorrow (I'm in europe). What i can tell you is that i started the process via mvn test as a Jenkins build and spawned subthreads from this one.
On Jul 25, 2013 10:15 PM, "JonathanRRogers" <...> wrote:
On Thursday, July 25, 2013 7:41:44 AM UTC-4, David Auzinger wrote:Hello!I've run into a problem while using Jenkins as a means to automate a JUnit/Selenium test.I'm working on an automated test for a Webshop using the Selenium WebDriver.I wrote the test multithreaded to us all available CPU-cores. Problem is, while the test runs as planned on a local machine when launche via Eclipse or Maven, when i'm launching it via Jenkins the CPU-load looks like only one of 4 cores is working. Is there any way to allow a single Jenkins-build to use all 4 Cores?--
Does your test run inside the Jenkins process or as a subprocess? Especially if the latter is true, I doubt Jenkins is the component limiting concurrency.
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/AWQtIDdFXYM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.