A daily build or nightly build is the practice of each day doing a software build of the latest version of a program. This is so it can first be compiled to ensure that all required dependencies are present, and possibly tested to show no 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 compiling and linking all the files that make up a 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 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 test (a term origintating in plumbing, where once repairs are complete, pipes are pressurized with smoke to see if any immediately visible leaks are present). 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.
Read more about Daily Build: Continuous Integration Builds
Famous quotes containing the words daily and/or build:
“Science, which cuts its way through the muddy pond of daily life without mingling with it, casts its wealth to right and left, but the puny boatmen do not know how to fish for it.”
—Alexander Herzen (1812–1870)
“We have been told over and over about the importance of bonding to our children. Rarely do we hear about the skill of letting go, or, as one parent said, “that we raise our children to leave us.” Early childhood, as our kids gain skills and eagerly want some distance from us, is a time to build a kind of adult-child balance which permits both of us room.”
—Joan Sheingold Ditzion (20th century)