Eclipse Community Forums: Buckminster » Avoid full workspace refresh during JUnit tests

Help

Home

Home » Archived » Buckminster » Avoid full workspace refresh during JUnit tests

Show: Today's Messages :: Show Polls :: Message Navigator

Avoid full workspace refresh during JUnit tests [message #1059656]

Tue, 21 May 2013 06:35

Christian Priebe

Messages: 2
Registered: May 2013

Junior Member

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

Report message to a moderator

Re: Avoid full workspace refresh during JUnit tests [message #1059772 is a reply to message #1059656]

Tue, 21 May 2013 14:39

Lorenzo Bettini

Messages: 1814
Registered: July 2009
Location: Firenze, Italy

Senior Member

On 05/21/2013 02:49 PM, Christian Priebe wrote:
> 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?

I had just noted this issue too; could that be the reason of
http://www.eclipse.org/forums/index.php/t/457638/ ?

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it

HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition

Report message to a moderator

Re: Avoid full workspace refresh during JUnit tests [message #1060611 is a reply to message #1059772]

Mon, 27 May 2013 10:17

Christian Priebe

Messages: 2
Registered: May 2013

Junior Member

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

Report message to a moderator

Previous Topic:	problems when running emma in Jenkins
Next Topic:	org.junit4:osgi.bundle: No provider was found that could resolve the request

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Nov 09 02:35:25 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter