Build pipelines

A build pipeline defines the automated process that transforms source code into deployable artifacts. It specifies the steps required to compile, test, validate, scan, and package the code.

In Build, you can define a pipeline as a Process and map each stage of the pipeline to a Job.

Pipeline stages as Jobs

A pipeline includes multiple stages. In Build, you can implement each stage as a Job.

A typical build pipeline consists of the following stages:

Table 1. Typical pipeline stages
Stages Tasks
Build Compile source code and generate binaries.
Test Run automated unit and integration tests.
Scan Perform security, compliance, or quality scans.
Package Create deployable artifacts.
Publish Upload artifacts to a repository.

You can create reusable Job templates for the above stages and add them in a Process to standardize execution across pipelines.

Multistage pipeline

Build supports multistage pipeline so that you can define multiple Job templates and combine them in a Process.

To configure a multistage pipeline, complete the following steps:

  1. Create Job templates for each required stage.
  2. Add the Jobs to a Process definition in the required execution order.
  3. Configure dependencies between Jobs to control execution flow.

The system runs the Jobs sequentially according to the defined order. Each Job represents a distinct stage. Downstream Jobs can consume artifacts produced by upstream Jobs. If a Job fails, the system stops or controls subsequent execution based on your configuration.

This multistage pipeline design enforces quality gates and ensures controlled progression.

Parallel pipeline

You can configure Jobs within a Process to run in parallel when no dependency exists between them.

To configure parallel execution, complete the following steps:

  1. Add multiple Jobs to the same Process stage.
  2. Do not define dependency relationships between those Jobs.
  3. Ensure sufficient system resources to support concurrent execution.

The system executes the Jobs simultaneously. Parallel execution reduces overall build time and optimizes resource usage.

Typical parallel execution scenarios are as follows:

  • Running multiple test suites simultaneously.
  • Running security scans and code quality analysis concurrently with testing.

For detailed procedures on creating Job templates and Process definitions, refer to Creating Jobs and Processes.