Selective Synching Across two (or more) BF Instances

We have two distinct Build Forge instances in our environment. Different application teams are assigned to one or the other for all of their projects to do builds, etc. We do, however, have a set of common libraries we provide for consistent integration with a number of tools.

The problem we are trying to solve is keeping the two instances in sync with respect to this common set of libraries and, of course, any associated environments, log filters, etc. One of our engineers has suggested doing selective replication of the backend DBs (oracle for us). This seems both tricky and dangerous to manipulate the DB without Build Forge's "knowledge". Anyone think this is a good/bad idea?

Has anyone solved this particular issue and would you be willing to share your general approach. I'm sure it can be solved with the services API but this will take a lot of code. Just want to be sure we start down the best path.

--Jeff

We have two distinct Build Forge instances in our environment. Different application teams are assigned to one or the other for all of their projects to do builds, etc. We do, however, have a set of common libraries we provide for consistent integration with a number of tools.

The problem we are trying to solve is keeping the two instances in sync with respect to this common set of libraries and, of course, any associated environments, log filters, etc. One of our engineers has suggested doing selective replication of the backend DBs (oracle for us). This seems both tricky and dangerous to manipulate the DB without Build Forge's "knowledge". Anyone think this is a good/bad idea?

Has anyone solved this particular issue and would you be willing to share your general approach. I'm sure it can be solved with the services API but this will take a lot of code. Just want to be sure we start down the best path.

--Jeff

My concern with export/import is that it doesn't handle snapshots properly.