My company is in the process of changing our version control tool from Rational ClearCase to Git. We have the following development scenario, and we are curious if there is an appropriate template for Git to achieve the same behavior as in ClearCase.
Here are some highlights of our situation:
- We have several discrete applications. Let me call these AppA, AppB and AppC.
- We also have certain files (build scripts, etc.) that are common to all projects. Let me call these Tools.
- For any cut AppA, AppB, or AppC code, we need a specific Tools code cut.
- Most of our developers never modify the code Tools.
For ClearCase, we modeled this as follows:
Components: app_a, app_b, app_c, tools
Projects: AppA, AppB, AppC, Tools
Project AppA includes app_a as a read and write component and tools as a read-only component.
Project AppB includes app_b as a read and write component and tools as a read-only component.
Project AppC includes app_c as a read and write component and tools as a read-only component.
Project tools include tools as a read / write component.
Each baseline for App * projects refers to a baseline for both app_ * components and tools. When developers rebuild to the recommended baseline, they pull the changes into both components.
Git , . / , . . , , ; .