Software build

From Wikipedia, the free encyclopedia
Jump to: navigation, search

In the field of computer software, the term build is similar to that of any other field. That is, the construction of something that has an observable and tangible result.[1] Historically, build has often referred either to the process of converting source code files into standalone software artifact(s) that can be run on a computer, or the result of doing so. However, this is not the case with technologies such as Perl, Ruby or Python which are examples of interpreted language. Therefore, it is better to define build management as the facilitation of the build process.

Functions[edit]

Building software is an end-to-end process that involves many distinct functions. Some of these functions are described below.

Version control[edit]

The version control function carries out activities such as workspace creation and updating, baselining and reporting. It creates an environment for the build process to run in and captures metadata about the inputs and outputs of the build process to ensure repeatability and reliability.

Tools such as Git help with these tasks by offering tools to tag specific points in history as being important, and more.

Code Quality[edit]

Also known as static program analysis/static code analysis this function is responsible for checking developers have adhered to the 7 axes of code quality; comments, unit tests, duplication, complexity, coding rules, potential bugs and architecture & design.[2]

Ensuring a project has high quality code results in fewer bugs and influences nonfunctional requirements such as maintainability, extensibility and readability, which have a direct impact on the ROI for your business.[3]

Compilation[edit]

This is only a small feature of managing the build process. The compilation function turns source files into directly executable or intermediate objects. Not every project will require this function.

While for simple programs the process consists of a single file being compiled, for complex software the source code may consist of many files and may be combined in different ways to produce many different versions.

Build tools[edit]

The process of building a computer program is usually managed by a build tool, a program that coordinates and controls other programs. Examples of such a program are make, Gradle, ant, maven, SCons and Phing. The build utility needs to compile and link the various files, in the correct order. If the source code in a particular file has not changed then it may not need to be recompiled (may not rather than need not because it may itself depend on other files that have changed). Sophisticated build utilities and linkers attempt to refrain from recompiling code that does not need it, to shorten the time required to complete the build. Modern build utilities may be partially integrated into revision control programs like Subversion. A more complex process may involve other programs producing code or data for the build process.

Tiers of Software Builds: manual compiles on individual developer boxes (tier 1), manual compiles on shared build box (tier 2), automated daily compile (tier 3), automated daily install built using installation software (tier 4), automated daily install deployed to QA boxes (tier 5) Continuous integration, and automated testing of the build and automatic creation of an install.

References[edit]

  1. ^ Lee, Kevin.A (1996). The Buildmeister's Guide - Achieving Agile Software Delivery. Lulu.com. p. 21. ISBN 978-1847283733. 
  2. ^ "SonarQube™ software". Retrieved 4 January 2014. 
  3. ^ Muschko, Benjamin. Gradle in Action. Manning Pubns Co. ISBN 9781617291302. 

See also[edit]