Hi guys,
The Groovy project is using Codehaus' Bamboo to build its sources. And perhaps because of some disk issue (but I don't know more yet for now), the Groovy builds are failing with the following message:
Is this something you've ever encountered? Any remedy you might think of? Since it appears to be an old Gradle version, I'm gonna suggest the Codehaus admin to install a more recent one.
Hopefully that'll help. Guillaume Laforge Groovy Project Manager SpringSource, a division of VMware |
Hard to say without seeing the full exception trace.
Any reason you aren't using the wrapper?
|
On Mon, Jan 28, 2013 at 10:59 AM, Luke Daley <[hidden email]> wrote:
Unfortunately that's all I had. Somehow, the registry.bin file was zero-length for some reason (probably some disk space issue Ben told me).
By nuking it, the builds started working again. It might be interesting to add some checks perhaps at the Gradle level in case some needed files like that registry.bin file are not corrupt or something.
No good reason not to.
We'll definitely have to adapt our builds to use the wrapper. Guillaume Laforge Groovy Project Manager SpringSource, a division of VMware |
In reply to this post by Guillaume Laforge
Guillaume, Are you getting this with gradlew? Sent from my iPhone
|
Hi Ken! No, this was with an installed Gradle. But I don't really have control of that at Codehaus. But I can certainly try to configure a shell to run ./gradlew instead.
Which is the right thing to do anyway. Although the underlying problem might have been present with gradlew as well, no idea. Guillaume On Mon, Jan 28, 2013 at 1:34 PM, Ken Sipe <[hidden email]> wrote:
Guillaume Laforge Groovy Project Manager SpringSource, a division of VMware |
Sent from my iPhone
|
On Mon, Jan 28, 2013 at 1:44 PM, Ken Sipe <[hidden email]> wrote:
Thank you, Ken. Well, the Groovy project is already using the wrapper, so there's nothing particular to do in this area, I think. So it's more on the Bamboo configuration side of things that I need to look up and see how I can update all our build plans to use ./gradlew instead of the Gradle artifactory plugin for building. Guillaume Laforge Groovy Project Manager SpringSource, a division of VMware |
In reply to this post by Guillaume Laforge
On 28/01/2013, at 9:05 PM, Guillaume Laforge wrote:
Definitely. We started doing this some time around the 1.2 or 1.3 release (I can't remember exactly which one), plus a bunch of other stability fixes in this area. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com |
On Fri, Feb 1, 2013 at 12:38 AM, Adam Murdoch <[hidden email]> wrote:
Thanks for the heads-up, Adam. Guillaume Laforge Groovy Project Manager SpringSource, a division of VMware |
Free forum by Nabble | Edit this page |