This is going to be tricky since there are a number of keys (eg, the
build results are stored on disk, etc). I think you might find it
easier to export them all using the data management tool and work on
merging the XML.
Let us know if you come up with a good solution or tool for this - it
be great to document or incorporate into Continuum in some way.
- Brett
On 23/09/2009, at 5:49 PM, Marc Lustig wrote:
Hi,
we have set up Continuum 1.3.4 and so far no new issues have been
identified.
For us, the major improvement of Continuum 1.3 is the ability to run
builds
in parallel.
So our plan is to merge our exsting 12 Continuum-instances into this
central
instance and distribute the jobs to different build queues.
What is the best practise to transer the projects of the old
instances into
the new central instance?
I guess there is no other way than to manually export and import the
database-tables, right?
So, could someone please advise which tables need to be copied in
order to
not violate some contraint?
The other issue is that the PK's are generated by the Continuum-app,
not by
the database.
So, when you import the records from the other instance, can I just
prepend
the next ongoing number, and ensure that foreign-keys are adjusted?
Sounds like a messy job, but configuring all those hundreds of
projects from
scratch maybe even worse.
--
View this message in context:
http://www.nabble.com/merging-databases-tp25531021p25531021.html
Sent from the Continuum - Users mailing list archive at Nabble.com.
