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: Any reason for making Jenkins workspace files private?
Date Mon, 01 Aug 2016 19:01:58 GMT
We deliberately block access to viewing the workspace directly - that
causes unneeded load on the master and agents and isn't hugely reliable in
the first place. As Alex said, if you want to view/use the output of your
build later, you should archive that output.

A.

On Mon, Aug 1, 2016 at 7:43 AM, Alex Harui <aharui@adobe.com> wrote:

> Isn't one of the post-build options to publish last successful artifacts?
> That's how we things like this.
>
> -Alex
>
> On 8/1/16, 1:20 AM, "Francesco Chicchiriccò" <ilgrosso@apache.org> wrote:
>
> >Hi there,
> >I have set up a Jenkins job for building Syncope SHAPSHOT docs at
> >
> >https://builds.apache.org/job/Syncope-master-docs/
> >
> >It works, but it seems that the workspace files (hence documentation
> >artifacts, in this case) are not available as anonymous:
> >
> >
> https://builds.apache.org/job/Syncope-master-docs/ws/target/generated-docs
> >/getting-started.html
> >
> >Any reason for this? Would it be possible to remove the protection for
> >such URLs? Thanks!
> >
> >Regards.
> >
> >--
> >Francesco Chicchiriccò
> >
> >Tirasa - Open Source Excellence
> >http://www.tirasa.net/
> >
> >Involved at The Apache Software Foundation:
> >member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
> >CXF Committer, OpenJPA Committer, PonyMail PPMC
> >http://home.apache.org/~ilgrosso/
> >
> >
>
>

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