PHP - 应用程序补丁构建
我正在尝试为我们的开发小组提出一个更好的解决方案来为我们的应用程序（PHP）构建补丁。
目前，我们每天向 SVN 提交，但不运行持续集成服务器，因为签入的代码可能存在错误。对于构建补丁，我们会检查上次构建的“修改日期”。但很多时候，我们已经开始开发新功能，或者进行其他错误修复，等等，这些都没有安排在补丁中。所以我们在测试服务器上运行时必须把它挑出来。
我正在寻找一种简单的方法来标记文件（我们使用 NetBeans 作为我们的 IDE），然后构建它。当我们进行自己的测试时，我们会对文件进行标记等。这可能只是文件中的文本字符串（不过，我们会在实时情况下将其删除）。
同样，我们的问题是试图跟踪哪些文件被标记为准备就绪，哪些文件正在开发中。
I'm trying to come up with a better solution for our development group to build patches for our applications (PHP).
We currently submit to SVN daily, but do not run a continuous integration server, as code checked in can be buggy. For building patches, we check against a "date modified", from the last build. A lot of times though, we're already starting development on new features, or have other bug fixes, etc that are not scheduled for the patch. So we have to pick it out when running against test servers.
What I'm looking for is an easy way to flag files (we use NetBeans as our IDE) and then build off that. As we go through our own testing, we'd flag the file, etc. This could simply be a text string in the file (we'd strip it out for live though).
Again, our issue is trying to keep track of which files are flagged as ready to go, versus what's currently in development.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我的问题是为什么不在分支机构发展？如果您为每个主要新功能创建一个分支，那么您将始终拥有一个“稳定”分支。然后，您只需从该稳定分支创建补丁，它只会包含已完成且经过审查的代码。当开发分支准备就绪时，测试后只需执行 SVN 合并即可将数据返回到稳定分支中...
尝试跟踪“生产”文件将成为主要的 PITA（特别是如果您有多个开发人员）。所以只要避免整个问题就可以了。
My question is why not develop in branches? If you create a branch for each major new feature, then you will always have a "stable" branch. Then you just create your patches off of that stable branch, and it'll only ever include completed and vetted code. When a development branch is ready to go, after testing just do a SVN Merge to get the data back into the stable branch...
Trying to keep track of "production" files is going to be a major PITA (Especially if you have multiple developers). So just avoid the whole problem.