Jenkins

Use this page when configuring team-level Jenkins metadata.

For repository scanning, deployment controls and GitHub topics, use Jenkins setup.

Team metadata required for pipelines

Each team needs configuration in the team-config file in the cnp-jenkins-config repository.

Send a pull request with your configuration.

All fields are mandatory. Copy another team’s config and adjust it to meet your needs.

sscs: # product name in Jenkinsfile_CNP, this will be a 'short name' that your team is known by
  team: "SSCS" # team 'display name', useful for longer more recognisable names for tagging
  namespace: "sscs" # Kubernetes namespace, usually the same as your 'product name'
  slack:
    contact_channel: "#sscs-tech" # public channel that you can be contacted at
    build_notices_channel: "#sscs-tech" # all build notices will be sent here
  tags:
    application: "social-service-child-support" # name that your service is known to by FinOps. If unsure, verify in #finops channel. Temporary placeholders are allowed.

Make sure your product name is not too long. Some Azure resources have length constraints and can fail if names are too long.

Jenkins build dashboard

Add a Jenkins build dashboard for your team by following the existing config patterns:

CFT: cnp-flux-config

SDS: sds-flux-config

Add similar configuration for your team, then raise a pull request and get it approved.

This page was last reviewed on 29 July 2026. It needs to be reviewed again on 29 January 2027 by the page owner platops-build-notices .

This page was set to be reviewed before 29 January 2027 by the page owner platops-build-notices. This might mean the content is out of date.