www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Schaefer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5647) Switch Tapestry website to svnpubsub via a buildbot build
Date Fri, 25 Jan 2013 19:21:13 GMT

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

Joe Schaefer commented on INFRA-5647:
-------------------------------------

I've created https://svn.apache.org/repos/infra/websites/production/tapestry/content
for you to prepopulate with content from your existing site.  This must be done BEFORE
we activate the builds.
                
> Switch Tapestry website to svnpubsub via a buildbot build
> ---------------------------------------------------------
>
>                 Key: INFRA-5647
>                 URL: https://issues.apache.org/jira/browse/INFRA-5647
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Buildbot, SvnPubSub
>            Reporter: Ulrich Stärk
>            Assignee: Joe Schaefer
>
> Equivalent to INFRA-4408, Tapestry wants to switch from Confluence autoexport to a buildbot+svnpubsub
build of its website. The parts to run the build are located at https://svn.apache.org/repos/asf/tapestry/tapestry-site/trunk/.
The configuration uses the same cxf-export-user as CXF and Camel do.
> I assumed the build parts need to be in SVN. If they can also be in Git I'd prefer to
put them there as Tapestry switched to Git.

--
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

Mime
View raw message