You can read about it here: http://trac.edgewall.org/wiki/MultipleRepositorySupport. It's in the sandbox section as http://trac.edgewall.org/browser/sandbox/multirepos. Christian last synced it with trunk 4 weeks ago, and I've encountered almost no issues using it (although I don't believe it supports [123:130] links yet).
I believe we'll be using Datamover for some maintenance going forward. From what I could tell it didn't quite do everything I needed at the time in an easy, automated fashion. I setup a th page for the script, http://trac-hacks.org/wiki/TracMergeScript, but the code isn't up yet. Right now the only working example is using our internal instances, so I'm going to build a generic example and post that. (Plus, the code is a bit ugly and lacking in even accurate docstrings at the moment). The way I handled namespacing was unfortunately manual, but therefore powerful and predictable. Because our existing wikis were something of a mess I ended up doing many renames. I have a csv file like the example below that explicitly renames each page. I used excel to put ProjectName/OldName for some of the projects that were just being strictly namespaced. It also will let you delete pages or pass them through unchanged. SourceTrac,SourcePage,DestTrac,DestName ProjectA,ReleaseNotes,Dev,ProjectA/ReleaseNotes ProjectB,ReleaseNotes,Dev,ProjectB/ReleaseNotes ProjectA,GetAnotherDeveloper,Intranet,Hiring/Jobs/Developer2007 It pads tickets by an arbitrary amount, so Project A gets a pad of 1000, Project B of 2000, so Project A ticket 123 becomes 1123 and B's 123 becomes 2123. It adds each milestone, component, and enum value. It updates links for wiki pages, milestones, tickets and changesets/revisions automatically. I hope that helps! I'm curious what you're situation might require that I haven't through of, as well. On Tue, Jun 3, 2008 at 12:53 PM, Stephen Moretti <[EMAIL PROTECTED]> wrote: > > 2008/6/3 Chris Mulligan <[EMAIL PROTECTED]>: > > After struggling with multiple (~13) disparate tracs I've built a system > to > > merge them down to two tracs. We're using wiki namespacing > > (Project/ReleaseNotes), and added a custom ticket field called "Project." > > We're using the excellent 0.12 MultiRepository branch plus a mercurial > > forest to keep separation. > > > > This is not the ideal solution, but so far it seems to be the most light > > weight and flexible method. We think it will serve our needs well, and > I'll > > be sure to post back with experience in a few months. > > > > I've got an ever increasing number of svn repos and trac environments > and I'm sure its all going to come unstuck soon unless I can get a > "single" port of call for ticketing/wiki-ing/user management/etc with > project separation in the mix. So I would love to hear some more > now... :D > > How did you go about merging the trac environments? > How do you enforce a project prefix for your wiki namespaces? > I'm using the trunk of Trac at the minute - I'm probably being blind, > but where do I find the MultiRepository settings/info? > > TIA > > Stephen > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
