Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EFA4F1756D for ; Fri, 13 Mar 2015 21:08:16 +0000 (UTC) Received: (qmail 8042 invoked by uid 500); 13 Mar 2015 21:08:16 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 8002 invoked by uid 500); 13 Mar 2015 21:08:16 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 7991 invoked by uid 99); 13 Mar 2015 21:08:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2015 21:08:16 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of busbey@cloudera.com designates 209.85.216.178 as permitted sender) Received: from [209.85.216.178] (HELO mail-qc0-f178.google.com) (209.85.216.178) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2015 21:07:51 +0000 Received: by qcwb13 with SMTP id b13so29800354qcw.9 for ; Fri, 13 Mar 2015 14:05:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=Ns4EobDJjW0HVUTYW0xUdb8cLpwbFmADKtOqn2ftBcM=; b=KUdzSKswC3eXa26IaVetQOxR3MBZy61D8SkYb23hlA8gGoWVwLnmXcGzOlg/zNMYVW dvDpYCY5eF5G1I5yGB4DV4KDU6p7l2VCsrd4hk32mnC3a2ABFOK08wXEc+73tew8gScw hJT4995R/39+/gsH+4r3T6IRJGJOk5oSmjZDueTJbTH7VE0r+UGcU/19+ikgxyD9bjsK 3r3EzBh8qBV42PEaStvMVRLdNZjnwwylif1z+Loc1YiWL3UwDhGTueKm2jIoylRphANz nnO9HfcTXx+P5pQyKgIm8LyVE5xQ524/AGJfFHLAI9yXT03DVtImVXc46+vzlG0CYqbL 77gQ== X-Gm-Message-State: ALoCoQm+n/UB0tuDGNJEs4UP/xmXBmWuV4lbDj52lLq2PMsGA5di/hMh0Z3cSyXaMui4cbQZAMMd X-Received: by 10.140.147.131 with SMTP id 125mr64891105qht.81.1426280734637; Fri, 13 Mar 2015 14:05:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.179.129 with HTTP; Fri, 13 Mar 2015 14:05:14 -0700 (PDT) In-Reply-To: <55034E81.6060106@gmail.com> References: <55031D37.7040506@gmail.com> <55032704.2070307@gmail.com> <550332F1.5040802@gmail.com> <55033B30.9050007@gmail.com> <55034E81.6060106@gmail.com> From: Sean Busbey Date: Fri, 13 Mar 2015 16:05:14 -0500 Message-ID: Subject: Re: More jenkins results To: "dev@accumulo apache. org" Content-Type: multipart/alternative; boundary=001a1137629489ddb4051131dc54 X-Virus-Checked: Checked by ClamAV on apache.org --001a1137629489ddb4051131dc54 Content-Type: text/plain; charset=UTF-8 +1 Thanks for doing this Josh. On Fri, Mar 13, 2015 at 3:54 PM, Josh Elser wrote: > Ok, I figured out how to do jenkins roles so that I can limit things down > to a specific set of jobs. > > I'll change my nightly 1.6 and master branch IT jobs to send to > notifications@ and we can go from there. I won't duplicate normal UT jobs > from apache jenkins. > > > Mike Drob wrote: > >> If it goes to notifications@ that is inherently a noisy list and I'm not >> worried about Josh taking a week off and a nightly build failing and >> sending an email. >> >> Christopher, would a set of keys held in escrow cover your concerns? >> >> Josh, thanks for doing this and keeping it running on your own dime. A >> real >> mensch! >> On Mar 13, 2015 2:43 PM, "Christopher" wrote: >> >> I'm not suggesting to impose external control. I just think it'd be >>> nice to know that, if the worst were to happen, and the service >>> started behaving badly while you were on vacation, we'd have some >>> recourse to control the automated notices to the email lists. >>> >>> [ If you do get hit by a truck, I *will* call you out on it ;) ] >>> >>> -- >>> Christopher L Tubbs II >>> http://gravatar.com/ctubbsii >>> >>> >>> On Fri, Mar 13, 2015 at 3:32 PM, Josh Elser >>> wrote: >>> >>>> If I wasn't clear the first time, anyone can view the results right now. >>>> >>>> I'm still not sure why you feel the need to impose external control over >>>> >>> a >>> >>>> system that I'm paying for and offering to provide as a service to the >>>> project. Unless I get hit by a truck, it's not like I won't be >>>> >>> responsive -- >>> >>>> and if I do rescind on that promise, you are more than welcome to call >>>> me >>>> out on it. Being unresponsive is one criticism that I don't think I've >>>> >>> been >>> >>>> given WRT Accumulo. >>>> >>>> IMO, the real question here is are people going to be looking at these >>>> results and doing anything with them? If they're just going to >>>> /dev/null, >>>> it's not worth it to me and I'll just do triage/fixing as I find time. >>>> >>>> >>>> Christopher wrote: >>>> >>>>> Looks fine in Chrome to me (but my Chrome is using my shared NSS >>>>> certificate store for my system). >>>>> >>>>> I can't think of anything immediately to configure... just speculating >>>>> that it might add utility when needed. At the very least, I would want >>>>> more than one person with the ability to turn off / modify the email >>>>> to the mailing list, if necessary. >>>>> >>>>> Being able to view the results without configuration permissions would >>>>> still be added value on its own, though. >>>>> >>>>> -- >>>>> Christopher L Tubbs II >>>>> http://gravatar.com/ctubbsii >>>>> >>>>> >>>>> On Fri, Mar 13, 2015 at 2:56 PM, Josh Elser >>>>> >>>> wrote: >>> >>>> Maybe this will help too. Last night's builds: >>>>>> >>>>>> >>>>>> >>>>>> https://secure.penguinsinabox.com/jenkins/job/Accumulo-1.6- >>> Integration-Tests/325/ >>> >>>> >>>>>> >>>>>> https://secure.penguinsinabox.com/jenkins/job/Accumulo- >>> Master-Integration-Tests/272/ >>> >>>> If you use Chrome, I don't think they accept StartCom SSL certs as >>>>>> trusted >>>>>> (so you'll get the crazy-scary red warning page), but it should be >>>>>> trusted >>>>>> by default in FF. >>>>>> >>>>>> >>>>>> Josh Elser wrote: >>>>>> >>>>>>> Presently, you can see the full workspace for the last job that was >>>>>>> >>>>>> run. >>> >>>> I'd have to look into Jenkins permissions, but what exactly do you >>>>>>> >>>>>> think >>> >>>> you would need to configure? >>>>>>> >>>>>>> Christopher wrote: >>>>>>> >>>>>>>> That might only be valuable if we could log on to it to view the >>>>>>>> test >>>>>>>> results and/or configure the jobs. >>>>>>>> >>>>>>>> -- >>>>>>>> Christopher L Tubbs II >>>>>>>> http://gravatar.com/ctubbsii >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Mar 13, 2015 at 1:24 PM, Josh Elser >>>>>>>> wrote: >>>>>>>> >>>>>>>>> For those who don't know, I run a Jenkins instance on a VPS I own. >>>>>>>>> I've been >>>>>>>>> running ITs for 1.6 and master nightly for some time now and it's >>>>>>>>> >>>>>>>> been >>> >>>> really nice to get these results. It has just enough resources to >>>>>>>>> >>>>>>>> run >>> >>>> through them reliably (some of the really heavy-handed tests fail on >>>>>>>>> it), >>>>>>>>> but personally it feels like a good baseline for ensuring the tests >>>>>>>>> are >>>>>>>>> runnable by anyone. >>>>>>>>> >>>>>>>>> If others feel like they might get value from it, I can set up >>>>>>>>> >>>>>>>> emails >>> >>>> to be >>>>>>>>> sent to the notifications@accumulo.apache.org list instead of just >>>>>>>>> >>>>>>>> to >>> >>>> myself. >>>>>>>>> >>>>>>>>> Thoughts/Opinions? >>>>>>>>> >>>>>>>> >> -- Sean --001a1137629489ddb4051131dc54--