同步GIT和ClearCase [英] Sync GIT and ClearCase

问题描述

我目前正在开发ClearCase，现在正在迁移到GIT。
但我们需要这种迁移方式，所有工作都将在GIT中完成，数据将同步到ClearCase流。我们将在GIT和CC中使用相同的分支名称和流名称，因此脚本编制不应该成为问题。这里的问题是，

有人可以建议哪个是同步CC和GIT的最佳模式吗？

1. 将CC中的所有Vob都作为GIT中的单个回购，并将CC中的主要流作为GIT中的各个分支。 - 单个GIT回购（VOBS）和许多分支（CC流）。 - 占用更少的空间，因为VOB被保留为许多分支机构的单个回购。

重要CC分支作为独立的GIT存储库，每个存储库具有所有CC的VOB。 - 许多CC分支的许多GIT回购 - 这将占用大量空间，因为VOB将被复制。

你认为哪种方法可以保持与ClearCase同步？

解决方案

CC中的Vob作为GIT中的单个回购，并且在CC中拥有主流作为GIT中的各种分支

不，是

将重要的CC分支作为独立的GIT存储库，并且每个存储库都具有所有CC VOB

不和

重读我对 Git限制 的回答，您不应该在Git仓库中尝试填充所有内容。

另见 Wha t是每个开发人员都应该知道的基本清晰概念？，以便比较ClearCase和Git。

Stream可以安全地作为分支导入。

但VOB不一定是Git Repo。

如果您使用的是UCM，我会推荐每个UCM组件一个Git回购。

无论如何，您需要在Git Repo中记录一种方法，以了解ClearCase视图用于同步的内容（通过简单 clearfsimport ）您的数据。
用于该ClearCase数据重新导入的视图将是一个自动关联到右侧VOB的右侧视图的UCM视图。

---

注意：我在如何将git连接到ClearCase？一个更简单的解决方案，但不导入所有历史记录在Git仓库中。

I am currently working on ClearCase and now migrating to GIT. But we need this migration in a way that all work will be done in GIT and the data will be synced backed to ClearCase stream. We will have the same branch names and stream names in both GIT and CC, so scripting shouldn't be a problem. The problem here is,

Can someone suggest which is the best model to sync CC and GIT

1. Have all the Vobs in CC as single repo in GIT, and have the major stream in CC as various branches in GIT. - Single GIT repo (VOBS) and many branches (CC streams). - This takes up less space as VOBs are kept as single repo with many branches.

2. Have important CC branches as independent GIT repositories and each repository having all the CC VOBs. - Many GIT repo for many CC branch - This will take up lots of space as VOBs will be replicated across.

Which do you think is the best way to keep it in sync with ClearCase

解决方案

Have all the Vobs in CC as single repo in GIT, and have the major stream in CC as various branches in GIT

No and yes

Have important CC branches as independent GIT repositories and each repository having all the CC VOBs

No and No

Re-reading my answer about Git limits, you shouldn't try to cram "everything" in a Git repo.
See also "What are the basic clearcase concepts every developer should know?" for a comparison between ClearCase and Git.

Stream can safely be imported as branch.
But VOBs are not necessarily a Git Repo.

If you are using UCM, I would recommend one Git repo per UCM component.

Anyway, you need to record in your Git Repo a way to know what ClearCase view to use to sync back (through a simple clearfsimport) your data.
The view used for that ClearCase data re-import will be a UCM view automatically associated to the right stream, for the right VOB.

---

Note: I mention in "How to bridge git to ClearCase?" a simpler solution, but which does not import the all history in a Git repo.

这篇关于同步GIT和ClearCase的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！