plugin a.b.c pom has one error
Non-resolvable parent POM: Could not find artifact.
a.b.c.pom:1.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local
POM @ line 5, column 11 - [Help 2]
the plugin a.b.c has a pom
where parent poms relative path is given
nightly build runs without any
Hello,
thank you for the suggestion - but I already tried that but it didn't
change the behaviour.
On Thursday, September 5, 2013 8:52:54 PM UTC+2, John Russell wrote:
I find I have much better luck in Execute shell build steps if I put
#!/bin/bash at the top.
It tends to make the
+1.
kill -9 as a first step is a very very very bad idea.
2013/9/4 Richard Bywater rich...@byh2o.com
Personally I wouldn't kill -9 the process straight away as then the
process has no chance to clean up after itself...
On Thu, Sep 5, 2013 at 12:57 AM, david.doug...@barclays.com wrote:
From my experience, and from what I think I've read somewhere (didn't check
the code), Jenkins will indeed try to launch the build on the last slave if
it's available for obvious reasons.
So, I suppose your slave was unavailable or busy (did you double-check the
builds that ran on it?) (see in
Not totally sure what you want, but seems more like a maven question than a
jenkins one.
2013/9/6 Gaurang shah gaurangns...@gmail.com
Hi Guys,
In the surefire reports on jenkins when a test case fails it shows both
stacktrace and stdout. Is there any way it shows stdout even when test case
Maven question. Please better post on Maven users mailing list next time.
As for your issue, move your log4j.properties file to src/test/resources.
Cheers
2013/9/6 Gaurang shah gaurangns...@gmail.com
Hi Guy,
I have configured log4j in my project, however the problem is when i run
that in
On Friday, September 6, 2013 12:39:54 AM UTC-4, Gaurang shah wrote:
Hi Guys,
I have my automation project configured on the Jenkins, Now everytime a
test case fails management is interested in knowing the reason.
Is it a bug in automation ?
is it a product bug ?
is it a timing or
Am 08.09.2013 22:02, schrieb Baptiste Mathus:
So, I suppose your slave was unavailable or busy (did you double-check
the builds that ran on it?)
Yes, I did. It was available, but idle for about 2 hours while the
second build was started on another slave. Neither the master, nor the
slave log
