[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS sandbox

["Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>]

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

Joe Schaefer commented on INFRA-4466:
-------------------------------------

There are a coupla features I'd like to see from maven to make use of the CMS
more palatable for large sites like maven.apache.org.  First, I would like the
ability to choose a target directory for the build from a command-line interface,
which will eliminate the need for a post-processing rsync job to copy the results.
That's not necessary for smallish sites, but is fairly important for multi-gigabyte ones.
So would a multi-threaded build process, but I assume that's more difficult to provide
near-term.

We also need to sort out how we're going to manage the "component" sites, either
as a part of the main site or as completely independent CMS-based sites.  Either
way, for the CMS to provide any significant advantage over straight svnpubsub
we will need a means of introspecting the build dependencies for a given target url
and making those corresponding source files available to the user via the CMS's
redirection feature.  Either providing a list of dependencies to select from, or a
"best guess" file to use, would be fine.  This would obviate the need for the use
of a "content/" dir for such things, which would only be capable of doing a file
match by globbing on the extension.


                
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
>                 Key: INFRA-4466
>                 URL: https://issues.apache.org/jira/browse/INFRA-4466
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: CMS
>            Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira