Perforce - 同步后生成补丁
我想在 Perforce 同步后保留一个“快照”。我不想将同步应用于所有目录树，而是想生成一个补丁文件。我将手动应用并检查结果（在编译和运行简单的测试用例之后）是否满意。如果结果正常，我将正式进行同步。如果是NG，我可以恢复到之前的“快照”并继续，而无需回滚的硬步骤。
我可以信赖“补丁”，因为它支持“撤消”。告诉 perforce 不要同步而是生成补丁，我该怎么做？
如果您能指导我如何通过脚本实现自动化，我将不胜感激。 p4v上的步骤就OK了。
问候， 托安乐
I would like to reserve a 'snapshot' after Perforce sync. Rather than applying sync to all directory tree, I would like to generate a patch file. I will apply manually and checking if the result (after compiling and running simple test cases) satisfies. I am going to do sync officially if result is OK. If it is NG, I can revert to previous 'snapshot' and continue without hard steps of rolling-back.
I can rely on 'patch' since it supports 'undo'. Telling perforce not to sync but to generate patch, how can I do that?
I appreciate if you can guide me how to automate via script. The steps on p4v is OK.
Regards,
Toan Le
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
正如迈克和乌鸦所建议的，这些都是好点。
但您也可以使用分支策略 - 将源代码分成 2 个分支。一个用于测试分支，一个用于发布分支。但在这里你还必须进行整合/合并。最好的方法是使用任何 CI 工具（例如 hudson、curisecontrol）来验证您的签入，作为增量构建的一部分，并自动运行所有必需的测试用例。
As mike and raven suggested, those are good points.
But also you can use branching strategies - make your source code into 2 branches. one for test branch and one for release branch. but here you will have to work on integration/merging as well. best would be to validate your check in perforce using any CI tools (such as hudson, curisecontrol) as part of incremental build and running all the required test cases automated.