Giri, I still see failures like this (50min ago), seems clover needs to be re-installed? Thanks!
BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch_3_3/branch-3.3/build.xml:973: ################################################################## Clover not found. Please make sure clover.jar is in ANT_HOME/lib, or made available to Ant using other mechanisms like -lib or CLASSPATH. ################################################################## On Wed, Aug 10, 2011 at 2:21 PM, Patrick Hunt <ph...@apache.org> wrote: > All the PA jira that have been updated since Jenkins went down, you > can find the list here: > https://issues.apache.org/jira/secure/IssueNavigator.jspa?sorter/field=updated&sorter/order=DESC > > Thanks! > > Patrick > > On Wed, Aug 10, 2011 at 1:25 PM, Giridharan Kesavan > <gkesa...@yahoo-inc.com> wrote: >> Do you have the patch number handy ? I can trigger the patch builds from the >> web UI this time. Pass on the jira numbers.. >> >> Whatever patch that you guys submit from now on will be picked up by jenkins >> automatically. >> >> Thanks, >> Giri >> >> >> >> On 8/10/11 1:19 PM, "Mahadev Konar" <maha...@hortonworks.com> wrote: >> >>> Ok, >>> the pre commit builds are up! Thanks a lot to Giri. >>> >>> Pat, I do not have login on the hudson build machines - builds.apache.org. >>> >>> Giri tells me that we can trigger builds for all the patches by just >>> specifying a patch name one at a time? >>> Do you know how to do that? >>> >>> thanks >>> mahadev >>> >>> On Aug 10, 2011, at 9:19 AM, Patrick Hunt wrote: >>> >>>> IIRC there was a way to trigger patch builds for all "patch available" >>>> jiras (Nigel did this a while back) - Mahadev can you check with Giri? >>>> If not we'll either have to trigger the build manually (committers >>>> only) or the contributor would need to "cancel patch" then resubmit >>>> (no need to reattach the patch file itself). >>>> >>>> On Tue, Aug 9, 2011 at 11:01 PM, Mahadev Konar <maha...@hortonworks.com> >>>> wrote: >>>>> Lakshman/others, >>>>> >>>>> Ill definitely send out a note on what to do. You are right that >>>>> folks might have to re upload the patches to the jira. The slaves are >>>>> still not fully functional yet. I expect them to be fully functional >>>>> tomorrow late evening (US time). >>>>> >>>>> Hope that helps >>>>> mahadev >>>>> >>>>> On Tue, Aug 9, 2011 at 10:44 PM, Laxman <lakshman...@huawei.com> wrote: >>>>>> Hi Mahadev, >>>>>> >>>>>> Do we need to resubmit the patches which were uploaded last week? >>>>>> Or Hudson will pick them up automatically? >>>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> From: Mahadev Konar [mailto:maha...@hortonworks.com] >>>>>> Sent: Wednesday, August 10, 2011 8:14 AM >>>>>> To: dev@zookeeper.apache.org; Giridharan Kesavan >>>>>> Subject: Re: Hadoop build machine update >>>>>> >>>>>> Thanks a lot Giri. >>>>>> >>>>>> I see something for ZK builds. Hopefully they'll be functional tomm. >>>>>> >>>>>> thanks >>>>>> mahadev >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Aug 9, 2011 at 7:35 PM, Giridharan Kesavan >>>>>> <gkesa...@hortonworks.com >>>>>>> wrote: >>>>>> >>>>>>> All, >>>>>>> >>>>>>> All the hudson slaves are back online. I was working on getting the >>>>>>> build >>>>>>> tools installed on all the new slaves and it looks like Its going to >>>>>>> take >>>>>>> some more time to change the build job configs before I could enable the >>>>>>> pre-commit jobs. >>>>>>> >>>>>>> Will get the precommit and nightly build jobs back online tomorrow. >>>>>>> >>>>>>> -Giri >>>>>>> >>>>>>> >>>>>>> On Tue, Aug 2, 2011 at 11:45 PM, Nigel Daley <nda...@mac.com> wrote: >>>>>>> >>>>>>>> Great! Thanks for getting the info. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> n. >>>>>>>> >>>>>>>> On Aug 2, 2011, at 8:05 PM, Eric Baldeschwieler wrote: >>>>>>>> >>>>>>>>> Hi Folks, >>>>>>>>> >>>>>>>>> I've talked to the folks at Yahoo about the build machines and am >>>>>> happy >>>>>>>> to report that an end to the blackout is in sight. >>>>>>>>> >>>>>>>>> 1) They need to reimage the machines, which is in progress and >>>>>> machines >>>>>>>> should be restored within a week (pessimistically). >>>>>>>>> >>>>>>>>> 2) They plan to reach out to the apache infrastructure team and change >>>>>>>> the admin of these machines to remove yahoo from the admin loop. This >>>>>>>> should avoid future outages and give apache more flexibility in >>>>>>>> managing >>>>>>> the >>>>>>>> machines. >>>>>>>>> >>>>>>>>> I'm told they will be posting more details today or tomorrow. >>>>>> Everyone >>>>>>>> there is committed to maintaining quality support for Apache and is >>>>>>>> concerned about the outage and making sure it does not repeat. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> E14 >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>> >> >> >
