Editing Daily build

{{Multiple issues|{{refimprove|date=February 2025}}
{{tone|date=February 2025}}}}

A '''daily build''' or '''nightly build''' is a [[software build]] of the latest version of a software system, run automatically on a daily/nightly basis. 

This is so it can first be [[compiler|compiled]] to ensure that all required dependencies are present, and possibly tested to show no [[computer bug|bugs]] have been introduced. The daily build is also often publicly available allowing access to the latest features for feedback.
In this context, a ''build'' is the result of [[compiler|compiling]] and [[Linker (computing)|linking]] all the files that make up a [[computer program|program]].  The use of such disciplined procedures as daily builds is particularly necessary in large organizations where many programmers are working on a single piece of software. Performing daily builds helps ensure that [[Software developer|developers]] can work knowing with reasonable certainty that any new bugs that show up are a result of their own work done within the last day.

Daily builds typically include a set of tests, sometimes called a "[[Smoke testing (software)|smoke test]]."  These tests are included to assist in determining what may have been broken by the changes included in the latest build.  The critical piece of this process is to include new and revised tests as the project progresses.

== Continuous integration builds ==
{{See also|Continuous integration}}
Although daily builds were considered a best practice of software development in the 1990s, they have now been superseded. [[Continuous integration]] is now run on an almost continual basis, with a typical cycle time of around 20-30 minutes since the last change to the source code. Continuous integration servers continually monitor the [[revision control|source code control system]]. When these servers detect new changes, they use a build tool to rebuild the software. Good practice today is also to use continuous integration as part of [[continuous testing]], so that [[unit test]]s are re-run for each build, and more extensive functional testing (which takes longer to perform than the build) performed as frequently as its duration permits.

==See also==
* [[Neutral build]]
* [[Smoke testing (software)|Smoke testing in software development]]

== References ==
{{Reflist}}

==External links==
*[http://www.stevemcconnell.com/ieeesoftware/bp04.htm IEEE Best software practices at Steve-McConnell]
*[http://www.joelonsoftware.com/articles/fog0000000023.html Joel-on-software]
*[http://cdimage.ubuntu.com/daily-live/current/ Daily builds of ubuntu, updated almost everyday], a good example of what a daily build is

[[Category:Software testing]]
[[Category:Extreme programming]]
[[Category:Computer programming]]


{{soft-eng-stub}}