Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: CMS
    • Labels:
      None

      Description

      Please help us creating a svnpubsubbed Site similar to logging.

      URL: https://svn.apache.org/repos/infra/websites/production/struts/content/

      We would like to let the CMS build our main site from this:
      http://svn.apache.org/repos/asf/struts/site/trunk/
      using maven.

      There will be several subsites which we want to populate manually.

      For example, the main site contains directories like:
      http://struts.apache.org/2.3.7/index.html

      We would like to exclude these directories via extpaths.txt and svn commit them by hand, when ever a new release has been published.

      Please assign a temporary sub domain first to give us the chance to commit the subsites before we go live.

      Thank you!

        Activity

        Christian Grobmeier created issue -
        Joe Schaefer made changes -
        Field Original Value New Value
        Assignee Joe Schaefer [ joes ]
        Hide
        Joe Schaefer added a comment -
        You need to complete the process of cms-ifying your source tree
        by moving src/ to content/.
        Show
        Joe Schaefer added a comment - You need to complete the process of cms-ifying your source tree by moving src/ to content/.
        Show
        Lukasz Lenart added a comment - [~joes] simple move current files from http://svn.apache.org/repos/asf/struts/site/trunk/src (or rather http://svn.apache.org/repos/asf/struts/site/trunk/src/site/?) to new folder http://svn.apache.org/repos/asf/struts/site/trunk/content ?
        Hide
        Joe Schaefer added a comment -
        Pretty much. You also need to adjust your pom file along the lines
        documented at http://www.apache.org/dev/cmsadoption#maven
        Show
        Joe Schaefer added a comment - Pretty much. You also need to adjust your pom file along the lines documented at http://www.apache.org/dev/cmsadoption#maven
        Hide
        Rene Gielen added a comment -
        As Christian pointed out in the issue description, it would be helpful to get a temporary SvnPubSub site location assigned to test the suggested configuration changes to apply to http://svn.apache.org/repos/asf/struts/site/trunk. Is that possible?
        Show
        Rene Gielen added a comment - As Christian pointed out in the issue description, it would be helpful to get a temporary SvnPubSub site location assigned to test the suggested configuration changes to apply to http://svn.apache.org/repos/asf/struts/site/trunk . Is that possible?
        Hide
        Joe Schaefer added a comment -
        That is the purpose of the staging site, to show you the results
        of the builds before they are made live.
        Show
        Joe Schaefer added a comment - That is the purpose of the staging site, to show you the results of the builds before they are made live.
        Hide
        Rene Gielen added a comment - - edited
        OK, understood.

        So you guys at Infra could trigger some helpful scripts to create https://svn.apache.org/repos/infra/websites/staging/struts (which currently is not present) and we could start to get our hands dirty with reconfiguration of our site sources. And once we're ok with what we see, we'd ping you to state we're ready to switch the production site. Correct?
        Show
        Rene Gielen added a comment - - edited OK, understood. So you guys at Infra could trigger some helpful scripts to create https://svn.apache.org/repos/infra/websites/staging/struts (which currently is not present) and we could start to get our hands dirty with reconfiguration of our site sources. And once we're ok with what we see, we'd ping you to state we're ready to switch the production site. Correct?
        Hide
        Joe Schaefer added a comment -
        Once your source tree conforms to the proper layout,
        that is what will happen, yes.
        Show
        Joe Schaefer added a comment - Once your source tree conforms to the proper layout, that is what will happen, yes.
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Joe Schaefer added a comment -
        Ping?
        Show
        Joe Schaefer added a comment - Ping?
        Joe Schaefer made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Lukasz Lenart added a comment - - edited
        Should I add subsites to content/resources/extpaths.txt to prevent deleting them? As mentioned in http://www.apache.org/dev/cmsadoption#maven
        Show
        Lukasz Lenart added a comment - - edited Should I add subsites to content/resources/extpaths.txt to prevent deleting them? As mentioned in http://www.apache.org/dev/cmsadoption#maven
        Lukasz Lenart made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Hide
        Joe Schaefer added a comment -
        Yes please!
        Show
        Joe Schaefer added a comment - Yes please!
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Lukasz Lenart added a comment -
        Done -> https://svn.apache.org/repos/asf/struts/site/trunk/

        I have a question about extpaths.txt file - should it contain also sub-folders generated during site generation?
        Show
        Lukasz Lenart added a comment - Done -> https://svn.apache.org/repos/asf/struts/site/trunk/ I have a question about extpaths.txt file - should it contain also sub-folders generated during site generation?
        Lukasz Lenart made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Hide
        Joe Schaefer added a comment -
        You only need to add the base path of the external tree to extpaths.txt.
        I will work on getting your CMS builds setup now.
        Show
        Joe Schaefer added a comment - You only need to add the base path of the external tree to extpaths.txt. I will work on getting your CMS builds setup now.
        Hide
        Joe Schaefer added a comment -
        Build results available at http://struts.staging.apache.org/
        Show
        Joe Schaefer added a comment - Build results available at http://struts.staging.apache.org/
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Joe Schaefer added a comment -
        I doubt you want css/ and images/ in your extpaths.txt filea
        as those paths are part of your maven build.
        Show
        Joe Schaefer added a comment - I doubt you want css/ and images/ in your extpaths.txt filea as those paths are part of your maven build.
        Joe Schaefer made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Lukasz Lenart added a comment -
        Thanks [~joes], I'll update extpaths.txt accordingly :-)
        Show
        Lukasz Lenart added a comment - Thanks [~joes], I'll update extpaths.txt accordingly :-)
        Lukasz Lenart made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Hide
        Lukasz Lenart added a comment -
        The builds are running [1], where can I check how the site looks like?

        [1] http://ci.apache.org/builders/struts-site-staging/builds/2
        Show
        Lukasz Lenart added a comment - The builds are running [1], where can I check how the site looks like? [1] http://ci.apache.org/builders/struts-site-staging/builds/2
        Hide
        Lukasz Lenart added a comment -
        Got it, but doesn't look good :\

        http://struts.staging.apache.org/
        Show
        Lukasz Lenart added a comment - Got it, but doesn't look good :\ http://struts.staging.apache.org/
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Lukasz Lenart added a comment -
        As I see the Archiva project is using two folders, in [1] keeps the Maven configuration of the site and deploys it to [2] and then SvnPubSub pushes changes to staging, right?

        [1] https://svn.apache.org/repos/asf/archiva/site/
        [2] https://svn.apache.org/repos/asf/archiva/site-content/
        Show
        Lukasz Lenart added a comment - As I see the Archiva project is using two folders, in [1] keeps the Maven configuration of the site and deploys it to [2] and then SvnPubSub pushes changes to staging, right? [1] https://svn.apache.org/repos/asf/archiva/site/ [2] https://svn.apache.org/repos/asf/archiva/site-content/
        Lukasz Lenart made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Hide
        Joe Schaefer added a comment -
        Probably, but I don't see how that helps you populate
        YOUR site. If I were you I'd talk to the maven people about
        how to get more content into your CMS source tree.
        Show
        Joe Schaefer added a comment - Probably, but I don't see how that helps you populate YOUR site. If I were you I'd talk to the maven people about how to get more content into your CMS source tree.
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Joe Schaefer added a comment -
        FYI: Keep in mind that infra is operating under a drop-dead date
        of Feb 1 before shutting off rsyncs. If you do not have this
        issue resolved by that date you will lose the ability to update
        and modify your existing website until this matter is settled.
        Show
        Joe Schaefer added a comment - FYI: Keep in mind that infra is operating under a drop-dead date of Feb 1 before shutting off rsyncs. If you do not have this issue resolved by that date you will lose the ability to update and modify your existing website until this matter is settled.
        Joe Schaefer made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Lukasz Lenart added a comment -
        Thanks [~joes] :-) Right now I'm trying to grasp how all this works ;-)
        Show
        Lukasz Lenart added a comment - Thanks [~joes] :-) Right now I'm trying to grasp how all this works ;-)
        Lukasz Lenart made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Hide
        Ralph Goers added a comment -
        I was very confused to when I went through the process of setting up the logging project. The process we use is documented at http://wiki.apache.org/logging/ManagingTheWebSite. Perhaps that will help clear things up?
        Show
        Ralph Goers added a comment - I was very confused to when I went through the process of setting up the logging project. The process we use is documented at http://wiki.apache.org/logging/ManagingTheWebSite . Perhaps that will help clear things up?
        Hide
        Lukasz Lenart added a comment -
        Thanks [~ralph.goers@dslextreme.com], but what I understand from the wiki is that I cannot use anymore Maven to manage my top site, only CMS. I can continue to use Maven to manage my subsites. Am I right?

        If so, is it possible to manage also the top site via Maven?
        Show
        Lukasz Lenart added a comment - Thanks [~ ralph.goers@dslextreme.com ], but what I understand from the wiki is that I cannot use anymore Maven to manage my top site, only CMS. I can continue to use Maven to manage my subsites. Am I right? If so, is it possible to manage also the top site via Maven?
        Hide
        Lukasz Lenart added a comment -
        Success!

        http://struts.staging.apache.org/

        Thanks for you help and patience :-)
        Show
        Lukasz Lenart added a comment - Success! http://struts.staging.apache.org/ Thanks for you help and patience :-)
        Hide
        Lukasz Lenart added a comment -
        One last question I hope :-)

        If I'll publish site right now and extpath.txt file contains the subsites' directories, will they remain untouched or will they be removed anyway?
        Show
        Lukasz Lenart added a comment - One last question I hope :-) If I'll publish site right now and extpath.txt file contains the subsites' directories, will they remain untouched or will they be removed anyway?
        Hide
        Ralph Goers added a comment -
        1. Even though you use the CMS you can still use Maven. Flume does that.
        2. As I understand it and my experience has been that once a directory is listed in extpaths.txt it is ignored by the CMS. Thus you have to manually maintain it yourself in the production site. You don't want to add anything under those directories to your staging site.
        Show
        Ralph Goers added a comment - 1. Even though you use the CMS you can still use Maven. Flume does that. 2. As I understand it and my experience has been that once a directory is listed in extpaths.txt it is ignored by the CMS. Thus you have to manually maintain it yourself in the production site. You don't want to add anything under those directories to your staging site.
        Hide
        Lukasz Lenart added a comment -
        Thanks [~ralph.goers@dslextreme.com] I'm going to publish the site right away :-)
        Show
        Lukasz Lenart added a comment - Thanks [~ ralph.goers@dslextreme.com ] I'm going to publish the site right away :-)
        Hide
        Lukasz Lenart added a comment -
        When I have tried to publish the site after entering log message I got:

        Error

        svnmucc: E125002: 'production/struts/content/1.0.2' not found

        Does it mean that I have to add all the subsites to production first?
        Show
        Lukasz Lenart added a comment - When I have tried to publish the site after entering log message I got: Error svnmucc: E125002: 'production/struts/content/1.0.2' not found Does it mean that I have to add all the subsites to production first?
        Hide
        Olivier Lamy (*$^¨%`£) added a comment -
        yes.
        As long as a directory is in extpaths.txt it must be here.
        That's why I recommended to you moving all your old sites to a single path (something like previous-versions) and reducing the number of lines in extpaths.txt will result in a faster publish (when you click the button :-))
        Show
        Olivier Lamy (*$^¨%`£) added a comment - yes. As long as a directory is in extpaths.txt it must be here. That's why I recommended to you moving all your old sites to a single path (something like previous-versions) and reducing the number of lines in extpaths.txt will result in a faster publish (when you click the button :-))
        Hide
        Lukasz Lenart added a comment -
        Yes I know, I'm working on that right now.
        Show
        Lukasz Lenart added a comment - Yes I know, I'm working on that right now.
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Waiting for user [ 10010 ]
        Hide
        Lukasz Lenart added a comment -
        The Struts site is ready for migration, could you make a switch and replace the current site with the CMS-published version?
        Show
        Lukasz Lenart added a comment - The Struts site is ready for migration, could you make a switch and replace the current site with the CMS-published version?
        Lukasz Lenart made changes -
        Status Waiting for user [ 10010 ] Waiting for Infra [ 10011 ]
        Hide
        Lukasz Lenart added a comment -
        Ping :-)
        Show
        Lukasz Lenart added a comment - Ping :-)
        Hide
        Joe Schaefer added a comment -
        Site is repopulating based on svnpubsub now.
        Good luck.
        Show
        Joe Schaefer added a comment - Site is repopulating based on svnpubsub now. Good luck.
        Joe Schaefer made changes -
        Status Waiting for Infra [ 10011 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Hide
        Lukasz Lenart added a comment -
        Thanks [~joes]!

        But there is one problem (I have overlooked it :\), we have an Ant task to download DTDs from the source and put them as a part of site generation, it looks like this below, how should the dest path look like to match SvnPubSub mechanism and allow publish DTDs with the site?

        {code:xml}
        <get src="http://svn.apache.org/repos/asf/struts/struts1/trunk/core/src/main/resources/org/apache/struts/resources/struts-config_1_0.dtd"
                 dest="${project.build.directory}/site/dtds/struts-config_1_0.dtd"
                 ignoreerrors="true"/>
        {code}

        https://svn.apache.org/repos/asf/struts/site/trunk/pom.xml
        Show
        Lukasz Lenart added a comment - Thanks [~joes]! But there is one problem (I have overlooked it :\), we have an Ant task to download DTDs from the source and put them as a part of site generation, it looks like this below, how should the dest path look like to match SvnPubSub mechanism and allow publish DTDs with the site? {code:xml} <get src=" http://svn.apache.org/repos/asf/struts/struts1/trunk/core/src/main/resources/org/apache/struts/resources/struts-config_1_0.dtd "          dest="${project.build.directory}/site/dtds/struts-config_1_0.dtd"          ignoreerrors="true"/> {code} https://svn.apache.org/repos/asf/struts/site/trunk/pom.xml
        Hide
        Lukasz Lenart added a comment -
        Ok, I was able to solve the problem :-)

        http://struts.staging.apache.org/dtds/
        Show
        Lukasz Lenart added a comment - Ok, I was able to solve the problem :-) http://struts.staging.apache.org/dtds/
        Gavin made changes -
        Fix Version/s Initial Clearing [ 12325964 ]

          People

          • Assignee:
            Joe Schaefer
            Reporter:
            Christian Grobmeier
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development