来自高层的消息要标准化我们的 SCM 系统。泥板上写着“Clear Case”。
我正在联系任何实际使用此配置的人 - 以获得最佳实践、提示和技巧、战争故事等等……
Sybase 源代码控制新闻组只返回蟋蟀的声音。
我们目前拥有大量积极维护的 Powerbuilder 11.5 和 EAServer 5.5 系统 - 因此 PBL 库文件级别的版本控制不是一个选项。
距离我们使用最新版本 12 还需要很长很长的时间——它删除了 PBL 文件并使用文本文件并作为 Visual-Studio 插件运行。
Word has come from upon high to standardize our SCM system. And upon the clay tablets was written Clear Case.
I am reaching out to anyone who is actually using this configuration - to get best practices, hints and tips, war stories, anything...
The Sybase Source Control newsgroup only gives back the sound of crickets.
We currently have a boatload of actively maintained Powerbuilder 11.5 and EAServer 5.5 systems - so version-ing at the PBL library file level is NOT an option.
And it will be a long, long time before we go to the newest version 12 - which removes the PBL file and uses text files and works as a Visual-Studio plug-in.
发布评论
评论（4）
我一直使用以下模式
_work.pbl
_last_一分钟_changes.pbl
1.pbl
2.pbl
3.pbl
...
我从 1,2,3... 导出对象并将它们签入clearcase。我使用 PowerGen 设置了夜间构建，以引导导入到网络共享。我使用脚本将这些 pbl 拉入我的视图中。我从 Clearcase 中检查一个对象并将其导入到我的 _work.pbl 中。进行更改，导出并将其签入clearcase。然后，触发器会触发 CI 构建，将对象导入到 _last_一分钟_changes.pbl 中，并根据前一天晚上的 pbl 重新生成它，然后将其存档到网络共享。
然后，我使用脚本刷新共享视图，并从我的 work.pbl 中删除该对象。当需要部署时，我们运行一个脚本，该脚本接受同步 pbl 并将它们转换为 pbd。
我在 4 个州的一个由 100 多名 powerbuilder 开发人员组成的团队中使用了这个流程，它对我们来说效果非常好。我们的应用程序有超过 12,000 个对象，但从未遇到过任何问题。
I've always used the following pattern
_work.pbl
_last_minute_changes.pbl
1.pbl
2.pbl
3.pbl
...
I export the objects from 1,2,3... and check them into clearcase. I set up a nightly build using PowerGen to do a bootstrap import to a network share. I use a script to pull those pbl's down into my view. I check an object out of clearcase and import it into my _work.pbl. Make my changes, export it and check it into clearcase. A trigger then fires a CI build that imports the object into the _last_minute_changes.pbl and regenerates it against the previous nights pbl's and then archives it to a network share.
I then refresh my view from the share using the script and delete the object from my work.pbl. When it comes time to deploy we run a script that takes the sync'd pbl's and turns them into pbd's.
I used this process for a team of over 100+ powerbuilder developers in 4 states and it woked really well for us. Our application had over 12,000 objects and we never had any problems.
我确实使用 ClearCase，但不直接与 PowerBuilder 项目一起使用。
ClearCase 手册有：
PowerBuilder 和 ClearCase 集成入门< /a>”文档。Sybase
信息中心 (11.5) 提到 影响源代码控制的设置。
无论是否为 PowerBuilder 项目，我建议：
I do use ClearCase, but not directly with PowerBuilder projects.
The ClearCase manual has:
Getting started with PowerBuilder and ClearCase Integration" document.
The Sybase infocenter (11.5) mentions settings affecting source controls.
PowerBuilder projects or not, I recommend:
我在之前的工作中使用过 ClearCase 和 PowerBuilder。
我们使用 IDE 集成的源代码控制，并对其进行设置，以便将各个对象作为原始文本对象（.sro、.srw 等）保存在 Clearcase 中。我不是导出对象的人，因此不幸的是我无法提供详细信息，但我认为 PB 至少可以为您做一些事情。无论如何，通过此配置，当我们从 PB 签入文件时，IDE 会自动将 .srX 文件签入 ClearCase。这是您需要的配置，以便您可以使用 ClearCase 工具查看更改的历史记录。
我们还使用 PowerGen 使用 ClearCase 中的源文件自动创建 PBL。这也是您要设置的过程。在此过程之前，我们必须手动将 PBL 检查到源代码管理中（！！）。我强烈建议您不要这样做 - 否则您无法真正保证 .srX 文件和 PBL 同步。
无论如何，这是一个简短的总结。如果您希望我澄清任何事情，请告诉我，我会尽力而为。祝你好运！
I used ClearCase and PowerBuilder at a previous job.
We were using the IDE-integrated source control, and had it setup so that the individual objects were saved in clearcase as raw text objects (.sro, .srw, etc). I was not the one that exported the objects so unfortunately I can't give details, but I think PB can do at least some of that for you. Anyway, with this configuration when we checked in a file from PB, the IDE would automatically check the .srX file into ClearCase. This is the configuration you need, so that you can view the history of your changes using the ClearCase tools.
We also used PowerGen to automatically create PBL's using the source files in ClearCase. This is also a process you want to set up. Previously to this process we had to manually check the PBL's into source control (!!). I strongly advise against you doing this - otherwise you cannot truly guarantee that the .srX files and the PBL's are in sync.
Anyway, that's a brief summary. Let me know if there's anything you would like me to clarify, and I'll do my best. Good luck!
我是源代码控制管理员，我已经一起使用 ClearCase 和 PowerBuilder（使用 IDE 集成）大约 7 年了。我们已将 PBL 对象（.srw、.sru 等）导出并保存在 ClearCase 中。 PBL 不在 ClearCase 中。我们还使用 PowerGen 代替 GLV 进行再生，因为 GLV 存在更复杂系统的问题。
ClearCase 与 PowerBuilder 完美集成（我们使用的是 9，我们正在升级到 12 以获得投资回报）。
在 IBM 网站上搜索“PowerBuilder 和 ClearCase 入门.pdf”。其中包含一些非常好的信息。
I am the Source Code Control Administrator and I have been using ClearCase and PowerBuilder together (using the IDE integration) for about 7 years. We have the PBL objects (.srw, .sru, etc) exported and in ClearCase. The PBLs are not in ClearCase. We also use PowerGen for regeneration instead of GLV because of GLVs issues with more complex systems.
ClearCase integrates beautifully with PowerBuilder (we are usign 9 and we are doing an ROI on the upgrade to 12).
Search IBM's website for "Getting started with PowerBuilder and ClearCase.pdf". That contains some very good information.