blocks|key|7108|text|我找到了VC/m，一个为Caché设计的版本控制系统。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|7109|如果您有使用它的经验，请随时添加您的评论。|7110|entityMap|0|LINK|mutability|MUTABLE|url|http://www.georgejames.com/vcm^0|4|4|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]]]]

I've found <a href="http://www.georgejames.com/vcm" rel="nofollow noreferrer">VC/m</a>, a version control system designed for Caché.

Feel free to add your comments if you have had any experiences with it.

blocks|key|3787624|text|另一种选择是TrackWare，它也是专门为Caché设计的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3787625|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gware.com/trackware.php^0|6|9|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]]]]

Another alternative seems <a href="http://www.gware.com/trackware.php" rel="nofollow noreferrer">TrackWare</a> which is also designed specifically for Caché.

blocks|key|3787647|text|如果您不怕开发工作，您可以进行一些开发，将studio与您当前的源代码控制工具挂钩。Cache中有一些挂钩，允许您检测对文件的修改并与您的源代码控制工具交互。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3787648|这里有一个pdf的链接，描述了这个基础：Using+the+Studio+Source+Control+Hooks。|offset|length|3787649|当然，使用此解决方案时，您必须在您这一方做大量工作。|3787650|entityMap|0|LINK|mutability|MUTABLE|url|http://www.google.fr/url?sa=t&source=web&ct=res&cd=5&ved=0CCcQFjAE&url=http%253A%252F%252Fdocs.intersystems.com%252Fdocumentation%252Fcache%252F2008_1%252Fpdfs%252FASC_Hooks.pdf&rct=j&q=Intersystem%2BCache%2Bversion%2Bcontrol&ei=hkAiS4_qKN_OjAea-9HTBw&usg=AFQjCNG4QnMyXMugW57uUa_SJNuxAzXedQ&sig2=_bD6792iaE_HQvZ5aMgrsg^0|0|K|11|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If you are not afraid by development work, you can make some development to hook studio to your current source control tool. There are hooks in place in Cache that allows you to detect modifications on files and to interact with your source control tool.

Here a link to a pdf the describes the basis :
<a href="http://www.google.fr/url?sa=t&amp;source=web&amp;ct=res&amp;cd=5&amp;ved=0CCcQFjAE&amp;url=http%3A%2F%2Fdocs.intersystems.com%2Fdocumentation%2Fcache%2F2008_1%2Fpdfs%2FASC_Hooks.pdf&amp;rct=j&amp;q=Intersystem+Cache+version+control&amp;ei=hkAiS4_qKN_OjAea-9HTBw&amp;usg=AFQjCNG4QnMyXMugW57uUa_SJNuxAzXedQ&amp;sig2=_bD6792iaE_HQvZ5aMgrsg" rel="nofollow noreferrer">Using the Studio Source Control Hooks</a>

Of course with this solution you will have to do a lot of work on your side.

blocks|key|7245|text|我使用的是Mercurial，虽然我确实使用了Cache+Studio源代码控制钩子(我没有使用ensemble)，但我认为基本上相同的解决方案也适用于您。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7246|关键是它是分布式的源代码控制。因此，钩子所做的一切就是在保存时将当前文件导出到我硬盘上的一个文件夹中，并将其签入到我的本地存储库。当事情在本地正常工作时，我会将其推送到中央存储库-换句话说，我只是以一种正常的方式使用分布式源代码控制。|7247|提交每一次保存都很好，因为这给了我一种方法，如果我把事情搞砸了，可以回滚，但这并不是真正必要的。您可以编写一些代码，当您从Cache命令提示符调用它时，它会将代码推送到本地存储库。|7248|对于分布式源代码控制，不支持签入和签出功能并不重要，您可以在推送到中央存储库时通过合并来处理这些问题(或者无论您决定如何构建存储库)。|7249|需要注意的是，对于Cache类定义，它们将以您未定义的格式导出为XML。它包括生成文件的时间戳和上次修改日期。这些欺骗了源代码控制系统，让他们认为自己已经改变了，而实际上并没有改变。因此，您必须至少对XML进行足够的解析才能将它们去掉。我不知道有什么标志可以从一开始就阻止它们的生成。|7250|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I'm using Mercurial and though I do use a Cache Studio source control hook (I'm not using ensemble) I think basically the same solution would work for you. 

The key is that it's distributed source control. So all the hook does is, on a save, export the current file to a folder on my hard drive, and check it in to my local repository. When things are working right locally, I push it to the central repository - in other words, I just use distributed source control in a normal way.

It's nice to commit each save since this gives me a way to roll things back if I mess something up, but it isn't really necessary. You could write something that pushes the code out to your local repository when you call it from the Cache command prompt.

With distributed source control the fact that check-in and check-out features aren't supported doesn't matter, you handle those issues by merging when you push to the central repository (or however you decide to structure your repositories).

One warning - for Cache class definitions, they are exported as XML in a format you don't define. It includes a time stamp of when the file was generated, and a last modified date. These fool the source control system into thinking they have changed when they have not. So you will have to parse the XML at least enough to strip those out. I don't know of a flag to prevent them from being generated in the first place.

blocks|key|2508535|text|回复晚了，但不管怎样-你可以看看来自Synerva的CodeTools。。CodeControl作为一个工作室插件工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2508536|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Late reply, but anyway - you can take a look at the CodeTools from Synerva. . CodeControl works as a Studio plugin

blocks|key|2515978|text|Synerva's+CodeTools为此提供了一个相当好的解决方案。已经在几个项目中使用了很长一段时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2515979|entityMap|0|LINK|mutability|MUTABLE|url|http://www.synerva.com/intersystems_technologies^0|0|J|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]]]]

<a href="http://www.synerva.com/intersystems_technologies" rel="nofollow noreferrer">Synerva's CodeTools</a> offer a pretty good solution for that. have been using that on several projects for quite a while.

blocks|key|3787715|text|Caché+Source+Control|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3787716|最好的解决方案！祝好运!|3787717|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cachewiki.org/index.php/Source_Control^0|0|K|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]]]]

<a href="http://www.cachewiki.org/index.php/Source_Control" rel="nofollow">Caché Source Control</a>

The Best Solution! 
Good luck!

I'm in a group which is starting to develop using InterSystems Ensemble (an integration framework built on top of InterSystems Caché). 

InterSystems has not made the Ensemble Management Portal source-control-aware and this seems a source of problems for development team we would like to address.

I would like to know which version control system are you using for Ensemble/Caché and how are you structuring your development process around it.

Version control for InterSystems Ensemble/Caché

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我所在的小组正在开始使用InterSystems集成(一个构建在InterSystems缓存之上的集成框架)进行开发。InterSystems没有使Ensemble Management Portal具有源代码控制意识，这似乎是我们希望解决的开发团队的一个问题来源。我想知道您对Ensemble/Caché使用的是哪个版本控制系统，以及您是如何围绕它构建您的开发过程的。

问InterSystems集成/缓存的版本控制
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问InterSystems集成/缓存的版本控制EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问InterSystems集成/缓存的版本控制
EN