Pipeline Data Object
The Pipeline data object defines and controls the execution of all the activities (and stages) to orchestrate and validate the build, and the deployment and testing activities required to securely deliver a modified Product Release.
The Pipeline data object shall have the following key data attributes:
Id: unique identifier of the Pipeline
Name: name of the Pipeline
Version: version of the Pipeline
Key Data Object Relationships
The Pipeline data object shall maintain the following relationships:
Pipeline to source code (n:m): the Pipeline is linked to a source code repository
Multiple Pipelines can be defined for one repository. Source code updates trigger the Pipeline to perform a number of tasks such as initiate static code analysis and build activities to create the Build Package (consisting of one or more build artifacts).
Pipeline to Test Plan (n:m): a Pipeline triggers the execution of several Test Plans (and associated Test Cases) such as those related to unit testing, performance testing, security testing, etc.
Pipeline to Build Package (1:n): a Build Package is created by one Pipeline (using one or more build tools)
Pipeline to Product Release Blueprint (1:n): the creation of a Product Release Blueprint is initiated and governed by one Pipeline
Pipeline to Change (1:n): a Pipeline can raise one or more Changes to inform stakeholders about new releases/changes, perform change impact assessment, and get formal approval (manually or automated)