Jenkins was wedged on there anyway, so I rebooted the VM. You should be good to
go again.
I'm not aware of any easy way to be able to kill that test from Jenkins, but
perhaps you could try this:
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkedProcessTimeoutInSeconds
-
On Mon, Mar 26, 2012 at 2:59 AM, Niklas Gustavsson wrote:
> On Tue, Mar 20, 2012 at 3:49 PM, Carsten Ziegeler
> wrote:
> > in the Sling project, we have one module which has a dependency to
> > some junit springsource artifact which is not in maven central.
> > There we added a repository instruc
We have again and again a problem to get our Windows build running after one of
our tests fails [1]. It looks like the test took to long. The process itself is
still existing and prevents Jenkins in the next build to delete the
camel-core-XXX.jar artifact. This is the reason for all next build f
