You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2016/08/03 10:18:20 UTC

[jira] [Closed] (INFRA-12363) Any reason for making Jenkins workspace files private?

     [ https://issues.apache.org/jira/browse/INFRA-12363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiriccò closed INFRA-12363.
------------------------------------------
    Resolution: Unresolved

As we are now using Buildbot, this issue is not relevant anymore.

> Any reason for making Jenkins workspace files private?
> ------------------------------------------------------
>
>                 Key: INFRA-12363
>                 URL: https://issues.apache.org/jira/browse/INFRA-12363
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Francesco Chicchiriccò
>
> 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!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)