Hi, Sorry guys, one change made was to point Maven3 Latest to a latest3 link as part of the node upgrades. The H* nodes have a 'latest' link but not a 'latest3' link (yet). Hence the breakage.
I have puppetised node H2 early so do please feel free to test - I have been watching and some precommit and normal builds alike seem to be preforming fine. I'll continue on with the rest of the H* nodes in a few hours and over the weekend. I'll be on HipChat #asfinfra (infra.chat) all w/end HTH Gav... On Fri, Jul 22, 2016 at 12:32 PM, Sean Busbey <bus...@apache.org> wrote: > I have a workaround now that I believe will work across the pre-puppet and > post-puppet hosts. I'll roll it out to impacted Hadoop jobs. > > Other interested folks, ping me if you need me. > > On 2016-07-21 17:46 (-0500), Sean Busbey <bus...@cloudera.com> wrote: > > I am having trouble finding a maven home related env variable that works. > > > > On Wed, Jul 20, 2016 at 10:37 AM, Allen Wittenauer > > <a...@effectivemachines.com> wrote: > > > > > >> On Jul 19, 2016, at 6:35 PM, Gav <gmcdon...@apache.org> wrote: > > >> > > >> > > >> A real PITA previously was maintaining of the 'latest' and > 'latest[1-3]' > > >> links. We are making > > >> good progress on improving these and will continue to do so. Please > shout > > >> up if something is a amiss. > > > > > > Would this be why MAVEN_3_LATEST__HOME on some of the H nodes > are empty as of a few days ago? e.g., > https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/100/console > > > > > > Thanks. > > > > > > > > > > > -- > > busbey > > >
