Skip to main content

Jenkins

To find out more about the common pipeline, please see its documentation.

There are Jenkins servers for both CFT (Civil, Family & Tribunal) and SDS (Shared Digital Services)

The steps to be followed below depend on what business area your application is in.

  1. Add the required GitHub topic to the repository to see your repository in Jenkins Org.

  2. Raise a pull request to add your repository to the Jenkins allowlist. Only repositories present in this file will be picked up by the Jenkins org scan.

    CFT: hmcts/cnp-jenkins-config/deployment-controls.yml

    SDS: hmcts/sds-jenkins-config/deployment-controls.yml

    Add an entry in the following format:

    - repo: https://github.com/hmcts/<your-repo-name>.git
  deployment-enabled: true

  3. Add a Jenkins build dashboard.

    CFT: cnp-flux-config

    SDS: sds-flux-config

  4. Scan the organisation manually on Jenkins if it doesn’t scan automatically.

  5. To allow Jenkins to deploy to production, you must add your GitHub repository to this list of approved repositories:

    CFT: hmcts/cnp-jenkins-config/environment-approvals.yml

    SDS: hmcts/sds-jenkins-config/environment-approvals.yml

Pipeline stages and deployment controls

The diagram below illustrates which pipeline stages are available depending on your deployment-enabled setting in deployment-controls.yml:

Common pipeline stages by deployment-enabled setting

  • Orange box — stages available when your repository is in deployment-controls.yml but deployment-enabled is not set to true: checkout master, build code, static QA
  • Purple box — all stages available when deployment-enabled: true is set, including: build/publish image, build infra, deploy, dynamic QA, tag image, and build infra (prod)

Without deployment-enabled: true, no Docker images will be published, no infrastructure will be applied, and no deployments to AKS will occur.

GitHub topics

Jenkins looks for repositories by searching for GitHub topics.

The topics are named after the Jenkins instance the repository will be built on and on CFT they are split alphabetically in a balanced split (most teams are before ‘j’ in the alphabet).

e.g. if your repository starts with div you look for where ‘d’ is in the topics, in CFT this would be jenkins-cft-d-i.

See the GitHub documentation on how to add a topic.

CFT Topics

  • jenkins-cft-a-c
  • jenkins-cft-d-i
  • jenkins-cft-j-z

SDS Topics

SDS repositories are not currently split, but they may be in the future.

  • jenkins-sds
This page was last reviewed on 1 June 2026. It needs to be reviewed again on 1 December 2026 by the page owner platops-build-notices .
This page was set to be reviewed before 1 December 2026 by the page owner platops-build-notices. This might mean the content is out of date.