We are prepping for a 9.4 → 10.1 upgrade and while we use GIT for our web code we have not used it for our OI code yet. I am trying to figure out the best method of using GIT with our developers in our test/development installation environment.

My first inclination was to create a separate OI application for each developer task and associate each of those applications to a separate GIT branch in a repository that is local to the test/development environment. I cannot, however, figure out how to assign an application's content (entities) to a particular branch.

Is there a best-practices approach for this type of development environment?

Appreciate your input.

PS – We have been using a system GIT installation (git-scm.com) along with Atlassian's Sourcetree GUI. I was able to successfully integrate both Sourcetree and GitExtensions UIs into OI 10.1 (one at a time of course :) ). We'd like to continue using Sourcetree if possible.

Before posting this I searched for GIT-related posts and could not find anything relelvant. As SOON as I posted I found the posts including Bob's video on the new OI GIT interface which was very helpful. I still believe we need to utilize branches so our developers can work simultaneously on their separate tasks.

OpenInsight's GIT integration does not know about branches.

My first inclination was to create a separate OI application for each developer task and associate each of those applications to a separate GIT branch in a repository that is local to the test/development environment

I think that is a good approach.

I cannot, however, figure out how to assign an application's content (entities) to a particular branch.

I think you would need to clone the repository for each OI.

That would let openinsight write to different physical locations. You would tell GIT that clone X was working on branch X.

Each OI would happily write to the GIT working folder for its clone. Managing the branches would occur outside of OI.

After merging that branch into the master you would delete the OI and its GIT clone.

Thanks Bob, I'll look into how that would work. Much appreciated.

Thanks again for your input Bob,

After reviewing your suggestion I moved to a procedure of

* creating new branch for our new task in our local 'cloned-from-remote' repository,

* checking out that new branch,

* cloning the local repository (now using the new branch) to a new local 'test' repository, and

* configuring OI to use this new repository ….

Theoretically this all worked fine until I tried applying the the local repository to a new OI-10 application. I've found that the name of the applications is tied into the repository content and I could not use it with a differently-named application.

I'm hoping I've just missed a step in the process, but cannot figure out what needs to be done. I'm assuming that teams of developers can work together in the same OI installation to simultaneously work on different tasks. It wouldn't be the first time an assumption blew up in my face though :)

Thanks for any advice.

View this thread on the Works forum...