Skip to main content
The CI/CD templates can be configured on a control plane level (available for customers using TrueFoundry in separate hosted control plane only). This customization can be used to add custom image scanning workflows, security scans etc to the CI/CD pipelines or add whatever custom logic user wants to add.

How do CI/CD templates get rendered?

TrueFoundry renders different CI/CD templates as shown in this document automatically based on the deployment.
All the templates can be found here.
There is a file called cicd-providers.yaml which lists the providers need to be enabled like github, bitbucket and gitlab. All other files contain templates to configure CI/CD based on different cases like:
  1. Whether image is built on TrueFoundry or built elsewhere.
  2. Whether the spec is stored as a yaml in your repository (complete GitOps) or not.
These are different templates for gitlab, bitbucket and github.

How to customize these templates for your Control Plane?

The CI/CD templates are supplied to TrueFoundry’s control plane via a config map. These config map values can be overridden by updating the values of truefoundry helm chart You will need to update the values of tfy-configs in the truefoundry helm chart. You need to define the content of cicd-providers.yamlwith your provider specific details. Here is the default file.
Apart from this you need to define all the the other templates of a particular provider (for e.g. github) by taking reference from the files in this folder. ( You should ideally change only the steps field in each yaml file (or maybe the description). No other field should be changed.)
Note
  • There must be a file named: cicd-providers.yaml in the CI/CD templates. You can use this as reference to create a CI/CD providers file:
  • All the keys must be file names of format *.yaml
  • You must define all the templates you need in the truefoundry values.