www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Bayer <andrew.ba...@gmail.com>
Subject Re: Heads up - Planning to disable anonymous workspace read access on builds.a.o
Date Wed, 21 May 2014 17:33:59 GMT
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.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message