www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-9175) Updating maven.apache.org site download.cgi with an executable flag does not work
Date Wed, 18 Feb 2015 21:47:11 GMT

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

Karl Heinz Marbaise updated INFRA-9175:
    Priority: Blocker  (was: Major)

> Updating maven.apache.org site download.cgi with an executable flag does not work
> ---------------------------------------------------------------------------------
>                 Key: INFRA-9175
>                 URL: https://issues.apache.org/jira/browse/INFRA-9175
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Buildbot, SvnPubSub, Website
>            Reporter: Karl Heinz Marbaise
>            Priority: Blocker
> I have changed the svn:executable flag in the https://svn.apache.org/repos/asf/maven/site/trunk
but unfortunately the flag is not transfered to the production site.
> In the stdiou output of the triggered build http://ci.apache.org/builders/maven-site-staging/builds/231/steps/shell/logs/stdio
you can't see that the download.cgi file has been updated, cause it contains only a change
in the above property.
> The result is that on production site / staging site the download.cgi does not have executable
permission which results in server error.
> Currently the work-a-round is to manually fix the property on production svn https://svn.apache.org/repos/infra/websites/production/maven/content...
> But the permission goes lost through the process of creation.
> After checking some things i found that the separate downloads in the areas of the plugins
like this http://maven.apache.org/plugins/maven-war-plugin/download.cgi don't work either...cause
every plugin has to have a separate download of the appropriate source release which makes
this issue more important.

This message was sent by Atlassian JIRA

View raw message