I should add the maven works perfectly fine outside of jenkins.
On Tuesday, May 22, 2012 2:45:42 PM UTC-7, Mark Cafaro wrote:
>
> Hi Sami,
>
> Here is the full console log (with some information removed for privacy
> sake):
>
> Started by user anonymous
>
> Reverting
> /Network/Servers/server/Vo
Hi Sami,
Here is the full console log (with some information removed for privacy
sake):
Started by user anonymous
Reverting
/Network/Servers/server/Volumes/Data/Users/hudson/.hudson/jobs/project/workspace/trunk
Updating https://server/svn/project/trunk
Fetching […]
Parsing POMs
[trunk] $ j
Any chance we could see the full console log? Is the build running on the
master or slave? How did you install Jenkins? Are you using the default maven
that comes with Mac?
-- Sami
Mark Cafaro kirjoitti 4.5.2012 kello 22.18:
> Is anyone aware of a workaround for the Maven crash on Jenkin's bu
Is anyone aware of a workaround for the Maven crash on Jenkin's build in OS
X that causes:
<===[JENKINS REMOTING CAPACITY]===>channel started
ERROR: Maven JVM terminated unexpectedly with exit code 134
In the one blog post I can find about it,
http://samuraism.jp/blog/2010/12/16/hudson_build_f
