Return-Path: <builds-return-3758-apmail-builds-archive=apache.org@apache.org>
X-Original-To: apmail-builds-archive@minotaur.apache.org
Delivered-To: apmail-builds-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 800F911142
	for <apmail-builds-archive@minotaur.apache.org>;
 Fri, 23 May 2014 19:12:13 +0000 (UTC)
Received: (qmail 6396 invoked by uid 500); 23 May 2014 19:12:13 -0000
Delivered-To: apmail-builds-archive@apache.org
Received: (qmail 5772 invoked by uid 500); 23 May 2014 19:12:13 -0000
Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:builds-help@apache.org>
List-Unsubscribe: <mailto:builds-unsubscribe@apache.org>
List-Post: <mailto:builds@apache.org>
List-Id: <builds.apache.org>
Reply-To: builds@apache.org
Delivered-To: mailing list builds@apache.org
Received: (qmail 5753 invoked by uid 99); 23 May 2014 19:12:13 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2014 19:12:13 +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 (athena.apache.org: domain of andrew.bayer@gmail.com
 designates 209.85.212.178 as permitted sender)
Received: from [209.85.212.178] (HELO mail-wi0-f178.google.com)
 (209.85.212.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2014 19:12:07 +0000
Received: by mail-wi0-f178.google.com with SMTP id cc10so1359472wib.17
        for <multiple recipients>; Fri, 23 May 2014 12:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=avOCSP7j1DAoZmPwhiMe8kK3Z707lN//CUNjH0KEpDE=;
        b=batvwHFamNg0e5ffUEl9eT7Gu4rENBFYz9qaQmyNd/V7VjTS0dinJE6IPRmVrMyPe3
         Izs3kqNrktrzDKjKzoE0YOitPW/KN9k10CvSpKa02NfDALwpUUMQi28+/FvEXCHXYufL
         3KaFiDc6eJnNbCweKYLRfLEiMNMTg93gud1Y4rqQY1g9/rKWWGienyNKvJ67kGjXQIsS
         LO4O5Qup8Qxgtj00P37ISf//F9N89rvsWZFM0ffPyQ2QtruR97Xl9xrxJ3Q+oRcBnfJo
         XHxkTlEBP/tObnflliZonwfeoZgeAcfojcfWnv/i0cdJiQj1jPbjn2nTBgR14scwAw+d
         kuKw==
X-Received: by 10.180.100.41 with SMTP id ev9mr5128759wib.22.1400872306090;
 Fri, 23 May 2014 12:11:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.236.161 with HTTP; Fri, 23 May 2014 12:11:26 -0700 (PDT)
In-Reply-To: 
 <CAPbPdOaTw0eAqMnrvBK506=snKbSxdtY3iwehkx1_Tq9d9JN7w@mail.gmail.com>
References: 
 <CAPbPdOaWKm7303+GeUdujCP9HAFg1ENKmwiXLk-s-kMChXxbVA@mail.gmail.com>
 <CAKprHVakEBc6=pK4phw=aYo3J9POV__8fGfhDJa3wUm7+QosGw@mail.gmail.com>
 <CA+ULb+uT1K26JFn0ozXi74qXnBdb6WzXxNsHk-dCawQtiHJeuA@mail.gmail.com>
 <CAPbPdOYn-6yUeve2xS6mhDN7p95ZCuu5xj-yBj4rCyeZj=FehQ@mail.gmail.com>
 <CA+ULb+u3gp-hSgdv06inOOwK3w0vnErRRoBxA3JhaTD_fDWUBA@mail.gmail.com>
 <CAPbPdOauFz6XRWpUrhKDfZzE1v2jouP7BmF6QhYwtSo-nBmqGg@mail.gmail.com>
 <CAPbPdOaTw0eAqMnrvBK506=snKbSxdtY3iwehkx1_Tq9d9JN7w@mail.gmail.com>
From: Andrew Bayer <andrew.bayer@gmail.com>
Date: Fri, 23 May 2014 12:11:26 -0700
Message-ID: 
 <CAPbPdOZQEh2KiiHfNb59EtLKF9jhCZkqrUhE7mJPiowESs-0HQ@mail.gmail.com>
Subject: Re: Heads up - Planning to disable anonymous workspace read access on
 builds.a.o
To: Roman Shaposhnik <rvs@apache.org>
Cc: David Nalley <david@gnsa.us>, "builds@apache.org" <builds@apache.org>,
	"infrastructure@apache.org Infrastructure" <infrastructure@apache.org>
Content-Type: multipart/alternative; boundary=f46d044402f42e2fa804fa160096
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d044402f42e2fa804fa160096
Content-Type: text/plain; charset=UTF-8

As an experiment, I'm now disabling *all* workspace read access to see if
that helps with hanging problems. FYI.

A.


On Wed, May 21, 2014 at 10:34 AM, Andrew Bayer <andrew.bayer@gmail.com>wrote:

> I've now removed anonymous read access to workspaces - let me know if
> there are any issues.
>
> A.
>
>
> On Wed, May 21, 2014 at 1:33 PM, Andrew Bayer <andrew.bayer@gmail.com>wrote:
>
>> That's fine usage, at least so long as there isn't another option out
>> there.
>>
>> A.
>>
>>
>> On Tue, May 20, 2014 at 9:02 PM, Roman Shaposhnik <rvs@apache.org> wrote:
>>
>>> On Tue, May 20, 2014 at 4:23 PM, Andrew Bayer <andrew.bayer@gmail.com>
>>> wrote:
>>> > Frankly, I'm fine with using jenkins archived artifacts for that -
>>> that's
>>> > not heavy load in my experience, though I'll watch out for any
>>> problems. The
>>> > issue has been serving files out of the slave workspace.
>>>
>>> I guess I wasn't explaining it well. Here's what I'm currently abusing
>>> Jenkins for:
>>>
>>> https://builds.apache.org/view/E-G/view/Giraph/job/Giraph-trunk-site/lastSuccessfulBuild/artifact/target/staging/
>>>
>>> This is a build of Giraph website that I would like to "publish" as
>>> part of our continuous integration efforts. Currently that
>>> publishing mechanism is to use URLs coming out of Jenkins. E.g.:
>>>
>>> https://builds.apache.org/view/E-G/view/Giraph/job/Giraph-trunk-site/lastSuccessfulBuild/artifact/target/staging/index.html
>>>
>>> I'd love to stop doing this, but I'm honestly not sure what
>>> else I can use.
>>>
>>> Thanks,
>>> Roman.
>>>
>>
>>
>

--f46d044402f42e2fa804fa160096--