www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <j...@apache.org>
Subject [jira] [Commented] (INFRA-12363) Any reason for making Jenkins workspace files private?
Date Tue, 02 Aug 2016 08:18:20 GMT

    [ https://issues.apache.org/jira/browse/INFRA-12363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403591#comment-15403591
] 

Francesco Chicchiriccò commented on INFRA-12363:
------------------------------------------------

[~ipv6guru] would you suggest to setup buildbot for the purpose (publishing SNAPSHOT docs
as result of Maven build)?

> 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)

Mime
View raw message