www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lieven Govaerts (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-2321) Import the Subversion podling's history into the primary ASF (public) repository
Date Tue, 10 Nov 2009 21:45:28 GMT

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

Lieven Govaerts commented on INFRA-2321:
----------------------------------------

Our buildbot master is polling the repository every few minutes to check for commits on trunk
and some branches. When the repository url changes, the master configuration should be changed
accordingly. 

The configuration file is stored in the svn repo here:
https://svn.collab.net/repos/svn/trunk/tools/buildbot/master/master.cfg

Either I or Justin Erenkrantz can deploy the updated configuration file and reload the buildbot
master process.

> Import the Subversion podling's history into the primary ASF (public) repository
> --------------------------------------------------------------------------------
>
>                 Key: INFRA-2321
>                 URL: https://issues.apache.org/jira/browse/INFRA-2321
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Greg Stein
>
> The Subversion podling will produce a dumpfile to be passed to Infrastructure for import
into the primary repository.
> There was a potential for a separate/distinct repository, but it appears the community
does NOT want that. We want to be present in the main repository. I will update this ticket,
should that status change in any way.
> The community wishes to load this code at /subversion/*. The Incubator requires /incubator/subversion/,
so a discussion needs to happen around that first.
> Based on prior discussion, it sounds like the repository will be placed into read-only
mode during the import. Thus, some kind of announcement/scheduling will need to be tracked
for this.
> We would also like to know how/where to transfer the dumpfile onto ASF hardware for loading.
> Joe says that a load will happen on a test repository first (great!). How can we get
cmpilato in to review the result of that? (and the time for load will give us an indication
of the readonly maintenance window)
> That's all I can think of so far.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message