You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/09/20 17:45:07 UTC

[jira] [Created] (INFRA-5302) stanbol.apache.org does not correctly sync to staging site

Bertrand Delacretaz created INFRA-5302:
------------------------------------------

             Summary: stanbol.apache.org does not correctly sync to staging site
                 Key: INFRA-5302
                 URL: https://issues.apache.org/jira/browse/INFRA-5302
             Project: Infrastructure
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: CMS
            Reporter: Bertrand Delacretaz


I've used "svn mv" to move folders around in the Stanbol website, and combined with the move to TLP at stanbol.apache.org it looks like the CMS is confused.

Things look good at http://stanbol.staging.apache.org/ but http://stanbol.apache.org doesn't match.

More details:

The website has moved to http://stanbol.apache.org/ today, and I have moved the contents of the old http://svn.apache.org/repos/asf/stanbol/site/trunk/content/stanbol folder directly under http://svn.apache.org/repos/asf/stanbol/site/trunk/content/

I've made some edits under site/trunk/templates to cause a full rebuild of the site, and published the site via the CMS a few times.

Right now the content is back under http://stanbol.apache.org/stanbol/ whereas a few minutes ago it was correctly under http://stanbol.apache.org/ - it looks like the published version oscillates between the old and new structure.

Also, using "force new working copy" at https://cms.apache.org/stanbol/ shows the old structure with a content/stanbol folder - using "update this directory" fixes that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (INFRA-5302) stanbol.apache.org does not correctly sync to staging site

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459697#comment-13459697 ] 

#asfinfra IRC Bot commented on INFRA-5302:
------------------------------------------

<variadic> svnwcsub didn't update on aurora; updated manually and bounced it.  Not entirely clear if eos had the same problem.  Along the way also tried a lazy publish (before the EU/US ambiguity surfaced).

                
> stanbol.apache.org does not correctly sync to staging site
> ----------------------------------------------------------
>
>                 Key: INFRA-5302
>                 URL: https://issues.apache.org/jira/browse/INFRA-5302
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CMS
>            Reporter: Bertrand Delacretaz
>
> I've used "svn mv" to move folders around in the Stanbol website, and combined with the move to TLP at stanbol.apache.org it looks like the CMS is confused.
> Things look good at http://stanbol.staging.apache.org/ but http://stanbol.apache.org doesn't match.
> More details:
> The website has moved to http://stanbol.apache.org/ today, and I have moved the contents of the old http://svn.apache.org/repos/asf/stanbol/site/trunk/content/stanbol folder directly under http://svn.apache.org/repos/asf/stanbol/site/trunk/content/
> I've made some edits under site/trunk/templates to cause a full rebuild of the site, and published the site via the CMS a few times.
> Right now the content is back under http://stanbol.apache.org/stanbol/ whereas a few minutes ago it was correctly under http://stanbol.apache.org/ - it looks like the published version oscillates between the old and new structure.
> Also, using "force new working copy" at https://cms.apache.org/stanbol/ shows the old structure with a content/stanbol folder - using "update this directory" fixes that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (INFRA-5302) stanbol.apache.org does not correctly sync to staging site

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot closed INFRA-5302.
------------------------------------

    Resolution: Fixed
    
> stanbol.apache.org does not correctly sync to staging site
> ----------------------------------------------------------
>
>                 Key: INFRA-5302
>                 URL: https://issues.apache.org/jira/browse/INFRA-5302
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CMS
>            Reporter: Bertrand Delacretaz
>
> I've used "svn mv" to move folders around in the Stanbol website, and combined with the move to TLP at stanbol.apache.org it looks like the CMS is confused.
> Things look good at http://stanbol.staging.apache.org/ but http://stanbol.apache.org doesn't match.
> More details:
> The website has moved to http://stanbol.apache.org/ today, and I have moved the contents of the old http://svn.apache.org/repos/asf/stanbol/site/trunk/content/stanbol folder directly under http://svn.apache.org/repos/asf/stanbol/site/trunk/content/
> I've made some edits under site/trunk/templates to cause a full rebuild of the site, and published the site via the CMS a few times.
> Right now the content is back under http://stanbol.apache.org/stanbol/ whereas a few minutes ago it was correctly under http://stanbol.apache.org/ - it looks like the published version oscillates between the old and new structure.
> Also, using "force new working copy" at https://cms.apache.org/stanbol/ shows the old structure with a content/stanbol folder - using "update this directory" fixes that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira