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 5CE8117EB7 for ; Fri, 13 Mar 2015 19:34:01 +0000 (UTC) Received: (qmail 31684 invoked by uid 500); 13 Mar 2015 19:34:01 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 31637 invoked by uid 500); 13 Mar 2015 19:34:01 -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 31625 invoked by uid 99); 13 Mar 2015 19:34:00 -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 19:34:00 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of josh.elser@gmail.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qc0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2015 19:33:35 +0000 Received: by qcvx3 with SMTP id x3so29204080qcv.0 for ; Fri, 13 Mar 2015 12:32:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Ql5YTEb73n3CmZ/OORVOHbJyoX6z+8ntRqFyK54jW3o=; b=InGewxODnRWSdKeXTKI0Fu6D5iXZIvTzHSlOh1gRyadLXAuBzO5qugUFYCIJuSJVlr n1Y8xvozad5gFFo8AXB35sKUVPZrB5kdl7JIOkQUoUyFKYtupu1IWKC9+cBdCkZ/Styz 1W6jpHpFK88tr9OeVE68OMhP2pciKqurcksRIzthc9ja9lMxsc7smNus2tOGX3Q5VSdu EhLrPYmjlmEz4VqESVZgFyNI5hJUAMcN4pGdo2xHftrxNJXu6wObEBKaXbl8wLuMJHMI i8wCaSBuuw/pdfBZZuGG7aocnQjOMgKD4hjInAVdwyttyk+Waod8lHosLE3kgImAJn64 phow== X-Received: by 10.55.55.4 with SMTP id e4mr87595535qka.97.1426275123875; Fri, 13 Mar 2015 12:32:03 -0700 (PDT) Received: from hw10447.local (pool-72-81-135-153.bltmmd.fios.verizon.net. [72.81.135.153]) by mx.google.com with ESMTPSA id f77sm2025495qka.9.2015.03.13.12.32.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Mar 2015 12:32:03 -0700 (PDT) Message-ID: <55033B30.9050007@gmail.com> Date: Fri, 13 Mar 2015 15:32:00 -0400 From: Josh Elser User-Agent: Postbox 3.0.11 (Macintosh/20140602) MIME-Version: 1.0 To: dev@accumulo.apache.org Subject: Re: More jenkins results References: <55031D37.7040506@gmail.com> <55032704.2070307@gmail.com> <550332F1.5040802@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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?