www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11247) OpenOffice CMS: No changes can be published to staging and production
Date Wed, 10 Feb 2016 22:03:18 GMT

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

Marcus commented on INFRA-11247:

The "hello" was a test by Daniel. AFAIK he has done this in staging only but not in SVN.

I expect to see the content from the ".../no-test/"index.html" file that I've committed into

> OpenOffice CMS: No changes can be published to staging and production
> ---------------------------------------------------------------------
>                 Key: INFRA-11247
>                 URL: https://issues.apache.org/jira/browse/INFRA-11247
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: CMS
>            Reporter: Marcus
>            Priority: Blocker
> First of all, sorry for priority as "Blocker" but we need attention and a fix. The problem
is existing since 3 weeks. Daniel Takamori (pono) has tried a few things but with no solution
so far.
> I've committed a new "no-test/" dir with files inside (Norwegian translations). But it
is not going to staging [1]. I can do changes in my CMS working directory or from the command
line from my local PC but it's not going to the staging build - or the production build [2].
> The same when committing changes in any other already existing files and dirs.
> [1] http://ooo-site.staging.apache.org/no-test/
> [2] http://www.openoffice.org/no-test/
> Please help. Thanks a lot in advance.

This message was sent by Atlassian JIRA

View raw message