“构建”和“构建”之间有区别吗？和CI？
我最近被分配的任务是负责在我的团队内定义新的流程和方法，以确保正确的开发流程。
我想知道术语“构建”和术语“CI”之间是否有任何显着差异。
我知道通常 CI 是在每次提交后构建项目的过程，以便更好地指示每个开发人员的提交级别。
执行 CI 时和运行正常“构建”时执行的构建或过程有什么区别吗？ （例如项目的每日构建）
谢谢
I've recently been assigned the task of being responsible for defining new processes and methodologies within my team, with regards to correct development processes.
I'd like to know if there is any significant difference between the term Build and the term CI.
I know that usually CI is the process of building your project after each commit to have better indication on the commit level for each developer.
Is there any difference in the build or in the process that is performed when doing CI and when running a normal "Build" ? (e.g. Daily build of the project)
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
构建过程是构建软件的所有过程（获取源代码、编译、打包、自动化测试等......）。
CI 是在提交时触发构建。
“每日构建”是构建的时间触发器。
The build process is everything that goes into building the software (getting the source code, compiling it, packaging it, automated tests etc...).
CI is the triggering of a build on commit.
A "daily build" is a time trigger for the build.
持续集成包含构建步骤等等 - 它可以运行自动化测试，在提交导致构建失败时向开发人员发送电子邮件，自动部署。所以我想差异在于每个概念所涉及的概念和步骤的数量。
Continuous Integration contains a Build step and much more - it may run automated tests, email developers when their commits caused a build failure, automatic deployment. So I guess the difference is in the number of concepts and steps involved in each one of them.