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 team > regarding what looks to be build usage of bits from some of their jobs' > 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é [1] http://wiki.apache.org/general/Jenkins#Are_there_recommended_or_mandatory_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 écrit : > 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 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 jobs' > workspaces, but I'd also like to nip this in the bud permanently by > requiring authentication for access to job workspaces. > > 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 be publishing from your build, you > can use the archive artifacts functionality. Does this sound reasonable to > everyone? > > A.
