blocks|key|2438928|text|我直接在Git视图中使用ClearCase。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2438929|然后，如果我有一个要同步的SVN，我可以将内容返回到SVN。|2438930|注意:对于直接在ClearCase视图中工作的工具，我必须使用快照视图，以便写入文件，即使这些文件尚未签出。然后，对于我认为已经完成的任何活动，我都会更新快照视图，它允许我列出所有被劫持的文件。我检查他们，然后登记他们。|2438931|在这种情况下(客户端的ClearCase回购)，我会看到使用SVN的问题是：|2438932|引入了另一个中央存储库(意为提交，您必须访问您的专用中心SVN存储库，对于“到客户端提交”，您必须访问中央ClearCase+VOB版本对象库，即ClearCase术语中的“存储库”)。|unordered-list-item|2438933|引入了另一个分支建模，其中在SVN中，它是一个目录中的廉价副本，而在ClearCase中，它是一个元数据(分支)，而不是一个目录。这意味着SVN签出的物理树可能与ClearCase中的快照视图更新不匹配，因为SVN签出的某些目录在ClearCase中根本不存在。|2438934|至少，对于Git，你有：|2438935|私有存储库(您没有添加其他每个人都应该访问的中央存储库)|2438936|相同的分支模型(至少在“不通过目录表示分支”时是这样)|2438937|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/^0|4|3|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|19|8|@]|9|@]|C|$]]|$1|M|3|N|5|L|7|1A|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1B|8|@]|9|@]|C|$]]|$1|Q|3|R|5|L|7|1C|8|@]|9|@]|C|$]]|$1|S|3|T|5|L|7|1D|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

I use <a href="http://git-scm.com/" rel="nofollow noreferrer">Git</a> directly within a ClearCase view. 
Then I could <a href="https://stackoverflow.com/questions/572893/cloning-a-non-standard-svn-repository-with-git-svn/572898#572898"><code>git2svn</code></a> back the content to SVN if I had a SVN repo to synchronize with.

Note: for a tool to work directly within a ClearCase view, I have to use a snapshot view, in order to write in files even if they are not checked out yet. Then for any activity I consider finished, I update the snapshot view which allows me to list all "hijacked" files. I check-out them, then check-in them.

<hr>

The issue I would see with working with SVN in this case (ClearCase repo for the client) would be to:

<ul>
<li>introduced another central repository (meaning to commit, you have to have access to your private central SVN repository, and, for "to-the-client commits", to have access to the central ClearCase VOB - Version Object Base, the "repository" in ClearCase lingo).</li>
<li>introduced another branch modeling, where in SVN, it is a cheap copy within a directory, whereas in ClearCase, it is a metadata (branch) not represented as a directory. That means the physical tree of a SVN checkout might not match a snapshot view update in ClearCase, because some of the directories checked out by SVN will simply not exist in ClearCase.</li>
</ul>

At least, with Git, you have:

<ul>
<li>private repository (you are not adding another central repository everyone should have access to)</li>
<li>same branching model (at least when it comes to "not representing a branch by a directory")</li>
</ul>

blocks|key|2438972|text|FYI+:它可能在某种程度上对你有用：从SVN迁移到ClearCase|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2438973|这并不同步数据，但如果需要迁移，它可能会有所帮助。|2438974|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1031389/moving-from-svn-to-clearcase^0|J|G|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Just FYI : It might be useful to you in some way : <a href="https://stackoverflow.com/questions/1031389/moving-from-svn-to-clearcase">Moving from SVN to ClearCase</a>

This doesn't sync the data, but if you need to migrate over, it might help out.

blocks|key|913126|text|如果clearcase有命令行支持，您将能够编写一个脚本来检查clearcase，并配置svn以便在提交代码时自动执行它(后提交钩)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|913127|entityMap|0|LINK|mutability|MUTABLE|url|http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks^0|1P|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If clearcase has command line support you will be able to write a script to check into clearcase, and configure svn to execute it automatically when code is committed (<a href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks" rel="nofollow noreferrer">post-commit hook</a>)

blocks|key|913185|text|该条描述了实现这一目标的几种方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|913186|http://www-01.ibm.com/support/docview.wss?ratlid=cctocbody&rs=984&uid=swg21258843。|offset|length|913187|基本上，变体：|913188|1)如果您对维护版本历史不感兴趣，只希望从最新版本或预选的配置开始，则可以使用clearfsimport命令。查看有关clearfsimport+(+clearfsimport)主题的ClearCase命令参考指南，以获得更多信息。|style|BOLD|913189|2)如果您需要版本历史记录，您可能需要评估开源工具svn2cc。|913190|解决办法：|913191|可以在Subversion中创建视图，表示开发流程中的某些里程碑。从这里，您可以使用前面提到的命令clearfsimport顺序地从每个视图导入版本。此场景中的clearfsimport命令将在每次运行元素时创建该元素的新版本，将标签自动应用于导入的版本。|ordered-list-item|913192|您可以尝试使用clearexport_cvs，因为Subversion存储库非常类似于CVS+(并发版本系统)，有关此导出实用程序的更多细节，请参见clearexport_cvs命令参考。|913193|entityMap|0|LINK|mutability|MUTABLE|url|http://www-01.ibm.com/support/docview.wss?ratlid=cctocbody&rs=984&uid=swg21258843^0|0|0|29|0|0|0|13|D|0|P|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|18|8|@$D|19|E|1A|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1B|8|@$D|1C|E|1D|J|K]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|R|7|1G|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

That article describes several ways for that:

<a href="http://www-01.ibm.com/support/docview.wss?ratlid=cctocbody&amp;rs=984&amp;uid=swg21258843" rel="nofollow noreferrer">http://www-01.ibm.com/support/docview.wss?ratlid=cctocbody&amp;rs=984&amp;uid=swg21258843</a>.

Basically the variants:

1) If you are not interested in maintaining version history and merely wish to start from the latest version or a preselected configuration, you can use the clearfsimport command. Review the ClearCase Command Reference Guide on the topic of clearfsimport (cleartool man clearfsimport) for more information.

2) If you require version history, you may want to evaluate the open source tool svn2cc.

WORKAROUNDS:

<ol start="3">
<li>It is possible to create views in Subversion representing certain milestones in your development stream. From there you can import the versions from each view sequentially using the aforementioned command clearfsimport. The clearfsimport command in this scenario will create a new version of the element each time it is run applying a label to the imported versions automatically.</li>
<li>You can try using clearexport_cvs, as the Subversion repository is very similar to that of CVS (Concurrent Versions System), see IBM Rational ClearCase Command Reference for more details on this export utility.</li>
</ol>

blocks|key|987406|text|是的，CollabNet专门为此目的提供了一种商业产品，称为CollabNet颠覆连接器。。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|987407|entityMap|0|LINK|mutability|MUTABLE|url|http://www.open.collab.net/products/integrations/svn2cc/^0|U|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Yes, CollabNet offers a commercial product specifically for that purpose, called the <a href="http://www.open.collab.net/products/integrations/svn2cc/" rel="nofollow noreferrer">CollabNet Subversion Connector.</a>

blocks|key|913274|text|我们需要这个来完成我的一个项目。该团队在svn中表现得更好，公司标准是ClearCase。因此，我编写了一个脚本，继续将主干迁移到clearcase，并在构建服务器上运行它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|913275|我把脚本放在这里：http://dvae.net/blog/2009/09/clearcase-to-svn/|offset|length|913276|我们所做的是在构建服务器上设置一个作业，该作业定期运行，并使用clearfsimport进行迁移。我们使用了Luntbuild作为构建服务器，但是巡航控制也可以正常工作。就像正常的构建一样，我们将脚本设置为只有当svn修改被检测到时才运行。我们每20分钟运行一次作业，因为ClearCase服务器位于不同的国家，所有操作都很慢，同步需要40分钟才能运行。我建议你尽可能多地跑步。|913277|该脚本基于ClearCase+UCM，如果您不需要删除“cleartool+mkact”，最后创建一个标签而不是基线。|913278|我将clearcase注释设置为自上次同步以来所有SVN提交的级联。|913279|我发现它是可靠的，而它失败的唯一原因是Clearcase触发器(像“邪恶的孪生”触发器)阻止了签入。当这种情况发生时，构建失败，Lunbuild发送一封电子邮件，然后我必须手动进行反向历史合并，以消除邪恶的孪生问题，提交和重新运行。|913280|entityMap|0|LINK|mutability|MUTABLE|url|http://dvae.net/blog/2009/09/clearcase-to-svn/^0|0|9|1A|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

We needed exactly this for a project I was on. The team was more comfortable in svn, and the corporate standard was ClearCase. So I wrote a script to continously migrate trunk to clearcase, and ran it on our build server.

I've put the script here: <a href="http://dvae.net/blog/2009/09/clearcase-to-svn/" rel="nofollow noreferrer">http://dvae.net/blog/2009/09/clearcase-to-svn/</a>

What we did was to set up a job on our build server that ran periodically and did a migration using clearfsimport. We used Luntbuild as the build server, but cruise control would work fine too. Like a normal build, we set the script to be run only when svn modifications where detected. We had the job run every 20 minutes as the ClearCase server was in a different country and all operations were slow and a sync took 40 mins to run. I suggest running as often as you can.

The script is based on ClearCase UCM, if you are not then have to remove the 'cleartool mkact' and at the end create a label instead of a baseline.

I set the clearcase comment to be a concatenation of all SVN commits since the last sync.

I found it reliable, and the only reason it would fail was if Clearcase triggers (like the 'evil twin' trigger) stopped the checkin. When that happens the build fails, Lunbuild sends an email, and I then have to manually do a reverse history merge to get rid of the evil twin problem, commit and re-run.

blocks|key|2439183|text|为此目的，Clearvision还提供了一个商业工具，可在这里获得：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2439184|http://www.clearvision-cm.com/clearcase-subversion-git-mercurial-integration.html|offset|length|2439185|它可以将clearcase与subversion、git或Mercurial同步。|2439186|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|29|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

There is also a commercial tool from Clearvision for just this purpose which is available here:

<a href="http://www.clearvision-cm.com/clearcase-subversion-git-mercurial-integration.html" rel="nofollow">http://www.clearvision-cm.com/clearcase-subversion-git-mercurial-integration.html</a>

It can sync clearcase with either subversion, git or Mercurial.

I have a client who is rather insistent about using Clearcase. Are there any tools/scripts that would allow my team to work against an SVN repository (or really anything other than Clearcase), but periodically automatically sync back changesets to the Clearcase VOB?

My thinking is that if such a tool exists, and it's automatic, reliable, and transparent the client might be pursuaded to allow us to work against SVN.

Thanks,
Kent

SVN to Clearcase Export

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个客户，他非常坚持使用Clearcase。是否有任何工具/脚本可以允许我的团队针对SVN存储库(或者实际上是Clearcase以外的任何其他东西)工作，但是定期地将更改集自动同步到Clearcase VOB？我的想法是，如果存在这样一个工具，并且它是自动的、可靠的和透明的，那么客户端可能会被追求允许我们使用SVN...

问SVN到Clearcase导出
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SVN到Clearcase导出EN