Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <herve.boutemy@free.fr>
To: builds@apache.org,
 "infrastructure@apache.org Infrastructure" <infrastructure@apache.org>
Subject: Re: Heads up - Planning to disable anonymous workspace read access on
 builds.a.o
Date: Sat, 17 May 2014 08:32:37 +0200
Message-ID: <4312632.IpXrOigWq2@herve-desktop>
User-Agent: KMail/4.13 (Linux/3.13.0-24-generic; KDE/4.13.0; x86_64; ; )
In-Reply-To: 
 <CAPbPdOaWKm7303+GeUdujCP9HAFg1ENKmwiXLk-s-kMChXxbVA@mail.gmail.com>
References: 
 <CAPbPdOaWKm7303+GeUdujCP9HAFg1ENKmwiXLk-s-kMChXxbVA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

since every committer can have an authenticated access to Jenkins, this=
 seems=20
reasonable to me

notice I don't really get what is "the archive artifacts functionality"=
: any=20
pointer appreciated, and I'll try to add explanations to our Jenkins be=
st=20
practices [1]

> am going to contact the Maven team
> regarding what looks to be build usage of bits from some of their job=
s'
> workspaces
are you talking about the dist-tool report [2], or something else?
Is a generated site like workspace or like archive?

Thank you for the hard work done.

Regards,

Herv=E9


[1]=20
http://wiki.apache.org/general/Jenkins#Are_there_recommended_or_mandato=
ry_Jenkins_settings_for_ASF_projects.3F

[2] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/=
site/

Le jeudi 15 mai 2014 13:55:21 Andrew Bayer a =E9crit :
> So from https://issues.jenkins-ci.org/browse/JENKINS-23056 it sounds =
like
> at least one of the problems we're having with Jenkins hanging is bec=
ause
> of attempts to access the workspace of jobs through the UI - when a s=
lave
> is slow or hanging and that kind of request is made, it can lock up t=
he
> whole UI. I've contacted the Mahout team regarding their linking to
> javadocs in job workspaces, and am going to contact the Maven team
> regarding what looks to be build usage of bits from some of their job=
s'
> workspaces, but I'd also like to nip this in the bud permanently by
> requiring authentication for access to job workspaces.
>=20
> My thinking is that the only legitimate reason to be accessing the
> workspace is if you need to in order to debug a failed build - otherw=
ise,
> if there's something that you want to be publishing from your build, =
you
> can use the archive artifacts functionality. Does this sound reasonab=
le to
> everyone?
>=20
> A.