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 <r...@apache.org> wrote: > On Fri, May 16, 2014 at 8:48 PM, David Nalley <da...@gnsa.us<javascript:;>> > wrote: > > On Thu, May 15, 2014 at 4:55 PM, Andrew Bayer > > <andrew.ba...@gmail.com<javascript:;>> > 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 be publishing from your build, you can use > the > >> archive artifacts functionality. Does this sound reasonable to everyone? > >> > > > > Makes sense to me. > > Jenkins is not a web server; and projects shouldn't be using it as such. > > Agreed 100%, but... ;-) > > ...what would be a recommend way to publish file trees for > the purposes of lets say contibnuos integration of things > like project websites and javadocs? IOW, which real webserver > on the ASF infra can serve that purpose? > > Thanks, > Roman. >
