Shared libraries

HMCTS maintains a set of shared pipeline libraries so that teams do not have to write and maintain their own build and deployment logic. Using them means your pipelines get the standard set of checks, security scanning, deployment patterns and fixes for free, and stay consistent with every other team on the platform.

Use the guide for the CI/CD system your repository builds with:

Library	CI/CD system	Typical use
Jenkins library	Jenkins	Building, testing and deploying applications and application infrastructure through the common pipeline
Azure DevOps libraries	Azure DevOps	Terraform plan/apply pipelines for platform infrastructure repositories
GitHub Actions library	GitHub Actions	Reusable workflows and composite actions, such as container build and push, Helm deploy and Terraform deploy

Each guide explains what the library is for, when to use it, how to import it into your repository, how versioning works, and links to real repositories using it today.

If you are not sure which applies to you, ask in #platops-help.

This page was last reviewed on 8 September 2026. It needs to be reviewed again on 8 March 2027 by the page owner platops-build-notices .