Difference between revisions of "Software build"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (→See also) |
Karl Jones (Talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 12: | Line 12: | ||
* [[DevOps]] | * [[DevOps]] | ||
* [[Test automation]] | * [[Test automation]] | ||
| + | * [[Software versioning]] | ||
== External links == | == External links == | ||
| Line 18: | Line 19: | ||
| − | [[Category: | + | |
| + | [[Category:Software development]] | ||
| + | [[Category:Software engineering]] | ||
Latest revision as of 19:01, 18 September 2016
In the field of software development, the term build is similar to that of any other field. That is, the construction of something that has an observable and tangible result.
Description
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 languages.
See also
External links
- Software build @ Wikipedia
