Hi Giuseppe,
I guess you mean your own Jenkins ?
The NoBoundException is cause by itests using RMI right ?
For Jenkins, I can share with you the configuration I did on our job in the
Apache Jenkins.
Regards
JB
On 09/07/2017 10:51 PM, Giuseppe Gerla wrote:
Hi all
I'm experimenting 2 strange behaviours with integration tests under jenkins.
The first problem is that often integration tests fail with a
java.rmi.NoBoundException. This is a randomic behaviour. The same tests
works fine on my pc.
The second problem is that when a test fails jenkins doesn't kill the test
process and in this way I have several ghost process.
Do you have some idea?
Following some additional information:
O.S. ubuntu 64bit
Jenkins -> 2.60.3
Karaf -> 4.0.9
pax-exam -> 4.9.1
maven 3.5.0
Regards
Giuseppe
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
