This guide covers adding a custom workflow in the build workflow.
We support adding custom bash scripts to our build workflow. For example, one may want to scan the source code before building and pushing the image to their docker registry.
Create the config map for your custom script to be able to mount that in our build workflow. You can either write a YAML spec and apply it or create it using kubectl
command as follows:
To add the above custom scrip to our build workflow, we need to first attach the config map as volume and then execute the script in the desired step. Please make the following changes in the values of the truefoundry
helm chart
Notes:
defaultMode
to 511
to make the file executable./scripts
by default.tfyBuild.truefoundryWorkflows.extraEnvs
.SOURCE_CODE_DOWNLOAD_PATH, DOCKER_REGISTRY_URL, DOCKER_REGISTRY_USERNAME , DOCKER_REGISTRY_PASSWORD, DOCKER_REPO, DOCKER_TAG, CALLBACK_URL
environment variables’ as these are reserved for internal usage. You may use them in your workflow if necessary.This guide covers adding a custom workflow in the build workflow.
We support adding custom bash scripts to our build workflow. For example, one may want to scan the source code before building and pushing the image to their docker registry.
Create the config map for your custom script to be able to mount that in our build workflow. You can either write a YAML spec and apply it or create it using kubectl
command as follows:
To add the above custom scrip to our build workflow, we need to first attach the config map as volume and then execute the script in the desired step. Please make the following changes in the values of the truefoundry
helm chart
Notes:
defaultMode
to 511
to make the file executable./scripts
by default.tfyBuild.truefoundryWorkflows.extraEnvs
.SOURCE_CODE_DOWNLOAD_PATH, DOCKER_REGISTRY_URL, DOCKER_REGISTRY_USERNAME , DOCKER_REGISTRY_PASSWORD, DOCKER_REPO, DOCKER_TAG, CALLBACK_URL
environment variables’ as these are reserved for internal usage. You may use them in your workflow if necessary.