Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-23 Thread Andrew Bayer
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 wrote: > I've now removed anonymous read access to workspaces - let me know if > there are any issues. > > A. > > > On Wed, May 21,

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-21 Thread Andrew Bayer
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 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 wr

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-21 Thread Andrew Bayer
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 wrote: > On Tue, May 20, 2014 at 4:23 PM, Andrew Bayer > wrote: > > Frankly, I'm fine with using jenkins archived artifacts for that - that's > > not heavy load in

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-20 Thread Roman Shaposhnik
On Tue, May 20, 2014 at 4:23 PM, Andrew Bayer 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

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-20 Thread Andrew Bayer
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. A. On Sunday, May 18, 2014, Roman Shaposhnik wrote: > On Fri, May 16, 2014 at 8:48 PM,

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-18 Thread Roman Shaposhnik
On Fri, May 16, 2014 at 8:48 PM, David Nalley wrote: > On Thu, May 15, 2014 at 4:55 PM, Andrew Bayer wrote: >> 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 - otherwise, if there's >> something that you want to b

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-17 Thread Hervé BOUTEMY
perhaps I read it too fast: IIUC, that can be like Maven's dist-tool report, ie a "Maven-generate site", as /site/ url, and not the /ws/target/site/ url which is the content from workspace If I read dist-tool output correctly [1] [JENKINS] Archiving site from /home/jenkins/jenkins-slave/workspa

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-17 Thread Gavin McDonald
Thanks Andrew for looking into this. Please go ahead and make the necessary changes once you are ready. Gav… On 17/05/2014, at 4:48 AM, David Nalley wrote: > On Thu, May 15, 2014 at 4:55 PM, Andrew Bayer wrote: >> So from https://issues.jenkins-ci.org/browse/JENKINS-23056 it sounds like at >>

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-16 Thread Hervé BOUTEMY
no, the workflow wouldn't be applicable with Jenkins: IMHO, such workflow should be published on Mahout website, with svnpubsub and extpaths.txt to avoid javadoc disappearing on each CMS change Regards, Hervé Le vendredi 16 mai 2014 23:28:59 Martin Desruisseaux a écrit : > Hello Andrew > > T

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-16 Thread Hervé BOUTEMY
since every committer can have an authenticated access to Jenkins, this seems reasonable to me notice I don't really get what is "the archive artifacts functionality": any pointer appreciated, and I'll try to add explanations to our Jenkins best practices [1] > am going to contact the Maven te

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-16 Thread Olivier Lamy
+1 -- Olivier On May 17, 2014 5:00 AM, "Andrew Bayer" wrote: > 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 because > of attempts to access the workspace of jobs through the UI - when a slave > is sl

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-16 Thread David Nalley
On Thu, May 15, 2014 at 4:55 PM, Andrew Bayer wrote: > 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 because of > attempts to access the workspace of jobs through the UI - when a slave is > slow or hang

Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-16 Thread Andrew Bayer
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 because of attempts to access the workspace of jobs through the UI - when a slave is slow or hanging and that kind of request is made, it can lock up the whole

Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o

2014-05-16 Thread Martin Desruisseaux
Hello Andrew Thanks for looking at this issue. On my side, I use the javadoc generated by Jenkins build every days. I often fix formatting issues and wait for the next Jenkins build for seeing if the fix worked. This is especially useful in class javadoc having tables, matrices or mathematical for