Upgrading existing Trac project to Bloodhound

[Anze Staric <an...@gmail.com>]

Existing Trac installation can be either upgraded to bloodhound or
migrated to a new bloodhound_install.

"upgrade"
1. Install our modified trac and bloodhound_modules
2. add required sections/options to the trac.ini in existing env
3. trac-admin upgrade with the newly-installed trac-admin

"migrate to a clean install"
1. Install our modified trac with bloodhound_* modules
1. create a fresh bloodhound environment using bloodhound_setup
2. restore database backup
3. modify database setting in trac.ini to point to the restored
database, copy any related files such as attachments to the new env.
4. trac-admin upgrade
5. trac-admin bhsearch rebuild

A currently missing third option is a way to move data from an
existing trac env to an existing bloodhound env (to consolidate data
from different envs to multiple projects in one env).

I used the migration when testing upgrade to multiproduct, as all I
had was a database backup. Has anyone tried the upgrade approach
recently? I've tried it on an empty project created by initenv, but do
not have any real trac envs to upgrade.


Anze

Re: Upgrading existing Trac project to Bloodhound

[Anze Staric <an...@gmail.com>]

> BTW , how do upgrade procedures behave with plugin data ... in practice ?

After some fixes to sql translation, TracSpamFilter (with existing
data) can be upgraded to multiproduct.

Existing plugin tables remain in the global product (without prefix)
and keep all the data. Product plugin tables (with prefix) are empty.
If I understand correctly, this is the way it is supposed to be.


Anze

Re: Upgrading existing Trac project to Bloodhound

[Anze Staric <an...@gmail.com>]

A few errors in sql translation related to plugin upgrades were fixed
earlier today (r1480186, r1480224).

In my setup, PastebinPlugin now upgrades to multiproduct without
errors and all the pastes survive the upgrade.


Anze

On Wed, May 8, 2013 at 4:42 PM, Olemis Lang <ol...@gmail.com> wrote:
> On 5/8/13, Olemis Lang <ol...@gmail.com> wrote:
>> On 5/8/13, Anze Staric <an...@gmail.com> wrote:
>>>> FWIW I will be using the instance deployed at
>>>> http://bh.web-sandbox.com . Is something like that what you are
>>>> looking for ?
>>>
>>> I was hoping for an instance with some real plugins, that are supposed
>>> to "just work" after upgrading to bloodhound.
>>>
>>
>> Like I mentioned in another thread [1]_ , I do have a test environment
>> with trachacks:PastebinPlugin activated and a few data ... but upgrade
>> procedure will not work .
>>
>> .. [1] citation needed , link not yet available in archive afaics
>>
>
> Oops ! Yes, it is ... my mistake . Sorry
>
> http://goo.gl/IZ8b5
>
> --
> Regards,
>
> Olemis.

Re: Upgrading existing Trac project to Bloodhound

[Olemis Lang <ol...@gmail.com>]

On 5/8/13, Olemis Lang <ol...@gmail.com> wrote:
> On 5/8/13, Anze Staric <an...@gmail.com> wrote:
>>> FWIW I will be using the instance deployed at
>>> http://bh.web-sandbox.com . Is something like that what you are
>>> looking for ?
>>
>> I was hoping for an instance with some real plugins, that are supposed
>> to "just work" after upgrading to bloodhound.
>>
>
> Like I mentioned in another thread [1]_ , I do have a test environment
> with trachacks:PastebinPlugin activated and a few data ... but upgrade
> procedure will not work .
>
> .. [1] citation needed , link not yet available in archive afaics
>

Oops ! Yes, it is ... my mistake . Sorry

http://goo.gl/IZ8b5

-- 
Regards,

Olemis.

Re: Upgrading existing Trac project to Bloodhound

[Olemis Lang <ol...@gmail.com>]

On 5/8/13, Anze Staric <an...@gmail.com> wrote:
>> FWIW I will be using the instance deployed at
>> http://bh.web-sandbox.com . Is something like that what you are
>> looking for ?
>
> I was hoping for an instance with some real plugins, that are supposed
> to "just work" after upgrading to bloodhound.
>

Like I mentioned in another thread [1]_ , I do have a test environment
with trachacks:PastebinPlugin activated and a few data ... but upgrade
procedure will not work .

.. [1] citation needed , link not yet available in archive afaics

-- 
Regards,

Olemis.

Re: Upgrading existing Trac project to Bloodhound

[Anze Staric <an...@gmail.com>]

> FWIW I will be using the instance deployed at
> http://bh.web-sandbox.com . Is something like that what you are
> looking for ?

I was hoping for an instance with some real plugins, that are supposed
to "just work" after upgrading to bloodhound.

Anze

Re: Upgrading existing Trac project to Bloodhound

[Olemis Lang <ol...@gmail.com>]

On 5/7/13, Anze Staric <an...@gmail.com> wrote:
> Existing Trac installation can be either upgraded to bloodhound or
> migrated to a new bloodhound_install.
>
[...]

> A currently missing third option is a way to move data from an
> existing trac env to an existing bloodhound env (to consolidate data
> from different envs to multiple projects in one env).
>

FWIW , we could abstract some details and work towards importing a
common «data backups» format that can be generated by similar systems
(including legacy Trac environments) . I've recently been reviewing
Bitbucket's format , which seems to be very interesting . I'll be
using it in the future .

https://confluence.atlassian.com/pages/viewpage.action?pageId=330796872
http://blog.bitbucket.org/2013/04/02/finnovation-brings-you-a-heap-of-new-features/

Is there any chance for us to implement such import/export data format
? That would make Bitbucket migrations easier . Does JIRA offer a
similar import / export functionality ?

> I used the migration when testing upgrade to multiproduct, as all I
> had was a database backup. Has anyone tried the upgrade approach
> recently?

I will have to upgrade a Trac 0.11 instance to BH trunk sooner rather
than later .

> I've tried it on an empty project created by initenv, but do
> not have any real trac envs to upgrade.
>

FWIW I will be using the instance deployed at
http://bh.web-sandbox.com . Is something like that what you are
looking for ?

I should also have a local version also containing pastes , and maybe
a few more things .

BTW , how do upgrade procedures behave with plugin data ... in practice ?

-- 
Regards,

Olemis.