Build process
The defined workflow that produces software artifacts from inputs such as source code and dependencies.
What is a build process?
A build process produces technical outputs from defined inputs, such as website files or an executable package. Inputs can include source code, dependencies and configuration. The workflow determines the steps: compilation, bundling and checks are possible parts. Not every build automatically includes all of them. Deployment and publication need separate consideration.
For a fictional portal, the team records the source revision, pinned dependencies, configuration and generated package. This allows investigation of the inputs behind a particular result. An existing output directory, however, establishes neither that all intended tests ran nor that the output is on the production system. Those require their respective check and deployment evidence.
Sources
Related terms
- CompilerA program that translates source code into another target representation.
- Runtime environmentThe environment in which a program executes and accesses the functions made available to it.
- BundlerA tool that groups connected modules and resources into files for delivery.
- Pull requestA proposal to integrate changes into a target branch, with context for shared review and discussion.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps