Glossary · Automation software engineering and architecture
Build pipeline
Also known as: Build workflow
German: Build-Pipeline
In software engineering, a build pipeline is an automated sequence of steps that turns source code into tested build artifacts, typically including retrieving the source, resolving dependencies, compiling, running static checks and automated tests, and publishing the results.
- Software engineering
In one sentence
A build pipeline is an automated sequence of steps that turns source code into tested, published build artifacts.
Example
Each merge to the main branch starts a build pipeline that compiles the PLC project with the engineering tool's command-line interface, runs unit tests and publishes the archive.
How it applies
- Engineering: A build pipeline makes builds reproducible and independent of individual workstations. In automation, it often needs licensed engineering tools on build agents and command-line or scripting interfaces to them.
- Quality: Pipelines are the natural place for Linting, static analysis, Automated test runs and Code coverage measurement. Failing steps stop the pipeline, so defects are found before release.
- Documentation: Pipeline logs and reports are evidence of how each artifact was produced and tested. Documentation sources, such as DITA maps or API references, can be built and checked in the same pipeline, so every software build comes with matching documentation.
Build pipeline vs. deployment pipeline
A build pipeline ends with a tested artifact. A Deployment pipeline takes that artifact through further environments to production. Together they form a CI/CD pipeline. Many teams use the terms loosely; project documentation should define which stages each pipeline covers.