As mentioned in yesterday's post "doing things right (making good use of tools )",CodeThe frequency of submission. At that time, I particularly emphasized"Ensure that the submitted code can be compiled",
The reason is "It is important for daily build ". I guess there are a lot of people who are not familiar with daily building, and there are also a large number of software companies staying in the hands-on workshop stage in China. So today we will come
Let's talk about the topic "Daily build. If you are already very good at using the "Daily build" method, you can skip this series to view other posts.
As an example, let's talk about what is "Daily build". Daily build is also called "Daily build" or "nightly build" in foreign languages. For specific definitions, see "here ". To put it simplyWholeSoftware ProjectAutomaticAfter compilation, the final output must be the same as the one delivered to the user (for example, what you finally submit to the user is an installationProgram, You must compile an installation package every day during the development process ).
To demonstrate that daily building is a very effective method, I can give you some examples of well-known software companies or well-known open-source projects:
1. The development process of almost all products within Microsoft is built on a daily basis.
2. I'm not sure if Google uses all products, but at least Google's Chrome browser is built on a daily basis.
3. Mozilla, a well-known open-source organization, is also widely used for daily building.
4. Well-known Linux releases of ubuntu are also built on a daily basis.
......
The list above can be very long. Taking so many examples, I just want to say that daily building is a kind of software engineering means. Especially for complex projects and large teams, its benefits are more obvious. Some may ask, what are the advantages? See "daily building of advanced software engineering [1]: benefits and advantages ".
Http://program-think.blogspot.com/2009/02/daily-build-0-overview.html