Use the following definitions to help you understand the release pipeline modeling and the artifact management workflow.


A script or the output of a build process. The artifact can be deployed or upgraded in a given stage.

Artifact types can be configuration files, application bits, or third-party software.

artifact management

A service that manages the artifacts over a range of local and remote repositories.

For example, managing a WAR file stored in the Maven repository.

gating rule

A set of rules that must be completed before the software changes are promoted and the next set of tasks starts in the subsequent stage.

The gating rules include testing rules and compliance rules. Gating rules that are associated with a pipeline are specific to an organization and applications.


A plug-in scenario that captures the specific configurations of a provider.


A collection of all the stages or environments in which a software change must pass through independently before it is released into production.

For example, development, test, user acceptance test, load test, staging, and production.


Service providers such as Jenkins, Bamboo, Bugzilla, Pivotal Cloud Foundry, and JIRA, which support various tasks.


Every stage in the pipeline defines a set of activities.

For example, deploy, test, approval through gating rules, and custom tasks.


An activity in a given stage.

For example, an activity can provision the machines, resolve the artifact, deploy the artifact, run the test, and so on. A manual task might be to open the port in a firewall.


Reports display the pipeline success and failure rate over time.