Builds on Hadoop 19 broke some time between May 6 and May 13 and have been bad
since then:
http://hudson.zones.apache.org/hudson/job/Hive-trunk-h0.19/buildTimeTrend
Anyone know what might have caused that?
Other Hadoop versions have been flaky as usual but not completely busted:
We need to delete the .ant directory containing the old ivy version in order to
fix it (and if we're using the same environment for both trunk and branches,
either segregate them or script an rm to clean in between).
Who can I contact to deal with the Hudson build environment?
JVS
I'm in favor of ditching the dynamic resolution of the ivy jar and just
checking
it into ivy/ or lib/. In general I don't think this is appropriate (that's
what Ivy is
for, right?), but I think this counts as a special case.
Carl
On Mon, Feb 8, 2010 at 10:42 AM, John Sichi jsi...@facebook.com
I'm fine with that too if someone wants to go ahead with that, but regardless,
I think we'll still need to do something to unwedge Hudson since ivy seems to
always find the old version in the .ant/lib directory if it's there.
JVS
On Feb 8, 2010, at 10:54 AM, Carl Steinbach wrote:
I'm in
All the Hive builds on Hudson are now back to normal, hopefully it won't
cry wolf again.
I have moved them back to Minerva and got access to clean out the tmp
directory, there's was a lot of random rubbish in there that somehow
broke the build.
I have opened this ticket to address the issue of
