CI/CD Pipelines

Continuous Integration and Deployment pipelines provide automation for creating and changing cloud environments.


A CI/CD Component is a compute resource responsible for taking cloud environment definitions, parameters, and tooling and orchestrating quality control processes to consistently verify and deploy these to target cloud environments. This brings together compute capability to follow defined workflows and storage capability for persisting outputs (including process metadata and/or records of deployed components).

This is a specialist compute workload, with a range of consumption options including self-managed infrastructure-as-a-service, managed platform-as-a-service, or fully-managed software-as-a-service.

The role of a CI/CD Component is to deliver:

  • Automated integration of cloud environment control software (build, aggregation, or compilation)
  • Automated testing and verification of cloud environment definitions and tooling
  • Automated deployment of cloud definitions using relevant tooling

Alongside Automation, Pipelines should be the only resources permitted to make changes to a cloud environment.


Both Continuous Integration and Continuous Delivery and Deployment are competencies described in the Cloudmarque Operating Model. Pipelines are a required system to implement the Cloudmarque Operating Model, providing a robust mechanism to control change in a cloud environment.


Cloudmarque workload components use a service locator pattern to identify the services they provide and specify dependencies. This component does not have any dependencies nor provide explicit services in the cloud environment, as it is part of the control plane for the environment.

Edit this page on GitHub

The content on this page is published under Open Source licenses via GitHub. To submit issues or provide feedback please visit the repository.