On Mon, Feb 10, 2014 at 8:26 AM, Olemis Lang <[email protected]> wrote:
> On Mon, Feb 10, 2014 at 11:00 AM, Ryan Ollos <[email protected] > >wrote: > > > On Mon, Feb 10, 2014 at 7:42 AM, Olemis Lang <[email protected]> wrote: > > > > > > > > On Feb 10, 2014 4:07 AM, "Joachim Dreimann" < > > [email protected]> > > > wrote: > > > > > > > > > > > > Begin forwarded message: > > > > > > > >> From: Kazys <[email protected]> > > > >> Date: 7 February 2014 10:32:23 GMT > > > >> To: [email protected] > > > >> Subject: Migrating multiple tracs as separate projects in > bloodhound. > > > >> Reply-To: [email protected] > > > >> > > > >> Hi, > > > >> > > > >> how could I migrate multiple tracs as separate projects in one > > > >> bloodhound installation? > > > >> > > > >> -- > > > >> Kazys > > > > > > > > > > > > > > There is no tested / supported way (that I know) to do this for > multiple > > > Trac projects but you could try with Bh rpc plugin > > > > > > http://bitbucket.org/olemis/bloodhound_rpc > > > > > > For a single environment the upgrade procedure is the way to go. > > > > > > > Saying this might be possible with a plugin without giving any > explanation > > on how to accomplish it isn't very helpful. > > > > > Just notice that the message was sent from my android tablet on the go ... > btw, the text was removed in previous reply > ;) > now I add that : > > - there's no such script out there (that I know) > - even in that case , there are a few missing features like e.g. it will > not be possible to import > with accurate timestamps e.g. in ticket comments > - There's no guarantee regarding data managed by plugins > > ... so , even if it's possible to do it I do not recommend this alternative > . You'll have to decide whether it's suitable in your particular case . > If you are suggesting that the use of RPC plugin somehow circumvents these difficulties please explain. So far you've failed to explain how the RPC plugin could be used in the migration. Eventually we should somehow support migrating from multiple trac environments, though handling plugin data for more than a few plugins would probably be outside the scope of what we could ever support.
