静态分析工具的使用 - 带有 Clear Case/Quest
我们正在定义我们的软件开发流程，并希望从小组中获得有关此主题的一些反馈。
我们的团队分布在美国、加拿大和印度，我想制定一些简单的标准规则，所有团队都将应用到他们的代码中。
我们使用 Clear Case/Quest 和 RAD
我一直在研究 PMD、CPP、checkstyle 和 FindBugs 作为开始。
我的想法是将这些放入 ANT 中并让开发人员手动运行它们。我意识到这样做你必须相信每个开发人员都会这样做。
另一个想法是在 IDE 中添加一些构建器，这些构建器将运行规则的子集（保持构建过程轻量），然后在签入代码时添加另一组（重度）。
其他一些理想是利用 Cruse Control 之类的东西，并将其设置为在 Clear Case/Quest 空闲时运行这些静态分析工具以及单元测试。
想知道其他人是否已经这样做了，是否成功或可以提供经验教训。
We are in the process of defining our software development process and wanted to get some feed back from the group about this topic.
Our team is spread out - US, Canada and India - and I would like to put into place some simple standard rules that all teams will apply to their code.
We make use of Clear Case/Quest and RAD
I have been looking at PMD, CPP, checkstyle and FindBugs as a start.
My thought is to just put these into ANT and have the developers run these manually. I realize doing this you have to have some trust in that each developer will do this.
The other thought is to add in some builders in to the IDE which would run a subset of the rules (keep the build process light) and then add another set (heavy) when they check in the code.
Some other ideals is to make use of something like Cruse Control and have it set up to run these static analysis tools along with the unit test when ever Clear Case/Quest is idle.
Wondering if others have done this and if it was successfully or can provide lessons learned.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们有：
注意：我们还没有真正设法使副本适用于我们不同的用户群（美国-欧洲） -香港），我们使用 CCRC 而不是多站点。
ClearCase 主要在欧洲使用，分析步骤在那里的夜间（UMT 时间）进行，并使用快照视图来确保它尽快进行（动态视图在访问大文件时涉及太多网络流量）。
We have:
Note: we haven't really managed to make replica works with our different user bases (US-Europe-Hong-Kong), and we are using CCRC instead of multi-sites.
ClearCase being mainly used in Europe, the analysis step takes place during the night there (UMT time), and use snapshot views to make sure it goes as quickly as possible (a dynamic view involves too much network traffic when accessing large files).
如果您的代码库不太大，我会使用 hudson 对 scm 更改运行静态分析，如果代码库太大，我会使用定期构建进行静态分析。
好吧，我无法抗拒...如果你的团队分散，你到底为什么要使用clearcase？作为必须使用它的人，当我们公司转向 Mercurial 时，团队速度极大地提高了。那些多站点垃圾真是太糟糕了。
I'd use hudson to run static analysis on scm changes if your code base is not too large, or on periodic builds if it is.
OK, i can't resist... If you team is spread out, why in the world would you use clearcase? As someone who had to use that, when our company switched to Mercurial the team velocity improved immensely. That multi-site junk is just awful.