This repository is an example project for k8s-jcasc-management-go or k8s-jcasc-management together with the jenkins-jobdsl-remote tool.

In a regular project, please do not combine both things together and create separate repositories for the job definitions! This means, that the directories:

• config
• projects
• templates

should be an own repository and the jenkins-dsl-jobs.json should be another repository.

The jenkins-dsl-jobs.json file should be under control of the project developers, and the previously mentioned directories should be under the control of the DevOps.

In the templates directory is a copy of the original one and contains new/customized templates in the cloud-templates directory. If you want to use own or modified templates, you have to copy all of them into this directory, which is then under your control.

The projects folder contains two examples of projects:

• example-project is a project with saved value files, which can be modified manually
• example-project-dynamic is a project which contains only the JCasC and the configuration file. The Helm values files are generated on-the-fly from the configuration.

More information:

• Medium Article Kubernetes and CI/CD — How to integrate in your development process
• Github k8s-JCasC-Mgmt tool
• Github k8s-JCasC-Mgmt example project
• Github k8s-JCasC-app-example
• Github k8s-JCasC docker containers
• Github k8s-JCasC helm charts example
• Github k8s-JCasC helmfile deployment example