rajeevn

 Profile Answers by rajeevn 

• Jun 16th, 2008

 

Night build approach is most suitable since the developers make the changes to product development code during usual work hours. Hence nightly build will generate the product images with the code checked in the day time.

It is most appropriate for product development with many compnents and teams working and having dependencies on others work for being able to unit and system test it.

Thirdly, it gives a fresh product image every morning so that to make a first head start for test team.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 9th, 2009

 

A software build is a process of converting source code files to executable code that can be run on computers.  A nightly build is a software build that is often automated and takes place at night when no one is likely to be working and there are no changes to the source code throughout the build process.  The results of the build are verified the following morning by running a smoke test. 

Nightly builds are often employed for software development processes running at high loads with short schedules. Not having them means that builds might possibly be created for the Quality Assurance team during the day using code which may be in the middle of major modifications. Nightly builds are an added level of assurance that builds will include only stable code.