A pipeline execution is one automated run of a service pipeline. It starts from a source-code change or manual trigger, processes defined steps, reports status, and produces artifacts for use across environments. section 3.4
A useful execution record provides:
- A unique identifier for retrieving the run’s parameters and reproducing its setup. section 3.4
- Clear success or failure notifications, including where and why a step failed and how long it took. section 3.4
- Logs from every step, plus links to produced artifacts and their publication locations. section 3.4
Figure 3.3 Service pipelines automate all the steps required to produce artifacts that can run in multiple environments. Service pipelines are often triggered by changes in source code, but are not in charge of deploying the created artifacts in a specific environment. They can notify other components about these new versions.
Service pipelines automate artifact production across environments while remaining separate from environment-specific deployment. section 3.4
