| Avoid full workspace refresh during JUnit tests [message #1059656] |
Tue, 21 May 2013 02:35  |
Eclipse User |
|
|
|
Hi,
we have a multi-project Eclipse RCP application which gets built on our Jenkins server. There are several test fragments, each containing the corresponding unit tests and a JUnit launch configuration.
On Jenkins the JUnit Buckminster task gets called for every launch configuration we have, like this:
junit -l com.example.p1.test/allTests.launch -o ${WORKSPACE}/testReport-p1.xml --stdout --stderr
junit -l com.example.p2.test/allTests.launch -o ${WORKSPACE}/testReport-p2.xml --stdout --stderr
junit -l com.example.p3.test/allTests.launch -o ${WORKSPACE}/testReport-p3.xml --stdout --stderr
Unfortunately Buckminster does a full workspace refresh after the execution of each junit task:
...
Doing full workspace refresh
Waiting for jobs to end
...
Since there are about ~10 test fragments and Buckminster does a full workspace refresh for each one of those the overall Jenkins job takes a lot of time.
Is there a way to change this behaviour and avoid those workspace refreshs? I guess it has something to do with the workspace configuration!? Can anybody give me a hint on how to change this?
Thanks in advance,
Christian
|
|
|
|
| Re: Avoid full workspace refresh during JUnit tests [message #1060611 is a reply to message #1059772] |
Mon, 27 May 2013 06:17  |
| Eclipse User |
|
|
|
Hey, thank you for your response. I have seen that other thread already, but I am not sure if it's the same issue or if both are correlated.
The JUnit test reports all have a size of below 1 MB and changing the log level doesn't have significant influence on the overall runtime (I already used DEBUG as log level, but also tried INFO in my latest test).
I still think the workspace refresh between the executions of the unit tasks are responsible for the, but I don't know why they are done in the first place.
Thank you
Christian
|
|
|
Powered by
FUDForum. Page generated in 0.02997 seconds
Home