Best practices to manage 2 disparate source repositories
I have a client scenario where there are 2 development teams which each works on separate repositories and these repositories are residing on different network and due to confidentiality, the 2 different networks are not connected. The files / components transferred are typically done using physical file media from one location to another.
What are the best practices in implementing the scenario using Jazz Source Control in RTC v3.0 ? Thank you. |
One answer
I have a client scenario where there are 2 development teams which each works on separate repositories and these repositories are residing on different network and due to confidentiality, the 2 different networks are not connected. The files / components transferred are typically done using physical file media from one location to another. https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/107569 This sounds similar to an existing enhancement request. The closest so far is being able to flow changes between two servers but this alone wouldn't fulfill your requirement. I suggest voicing your support in the enhancement. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.