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
] 
Search
Help
Register
Login
Home
