CasC Jenkins

[danielstankw]

Have been using Jenkins for few years now, in the past I tried various methods for configuring CasC, but each time I failed. Current setup involves storing yaml inside yaml i.e. CasC configuration inside values.yaml file.

I have tried:

1. Placing casc.yaml config files in the folder of "/var/jenkins_home/casc_config/jenkins.yaml but I wasnt able to get it to work
2. Adding git repo with yamls in ConfigUrls didnt work.

Did anyone managed to get it to work and would be kind enough to share their setup?
The CasC helm chart setup is a nightmare

[vazhnov]

#743 ?
#218 ?

[danielstankw]

I generated jenkins.yaml that I placed in BitBucket, but nevertheless the CasC fails and cant start up the pod

[eightnoneone]

Can you clarify? Is the question that you are intentionally trying to do JCasC in a way that is outside of this helm chart's implementation of JCasC?

Or are you providing something like this and it's not working?

controller:
  JCasC:
    configUrl: https://somehost/jenkins.yaml

Can you provide any examples of relevant values.yaml?

[SampsonCrowley]

@eightnoneone they (and the two other issues that have been pretty much ignored) are saying this helm chart's way of managing JCasC is painful to onboard, and not the best way to manage it.

without the helm chart, you have the option of pointing JCasC at a local directory on the jenkins master, via CASC_JENKINS_CONFIG but this helm chart specifically disallows that; instead making us create multiple values files and explicitly pass each individual file to the helm upgrade/create statement. to just always include all files in a directory, 1, the configs all have to use the | syntax nested under controller.JCasC instead of just being plain JCasC yaml files, and 2 we have to come up with a script to actually pass each individual file as a flag to the helm chart.

it would be MUCH simpler and MUCH less confusing if it just actually followed the structure of JCasC, and to support a directory, the chart created a configmap from the whole directory, and placed that directory in the pod at /var/jenkins_home/casc_configs

or if we don't want to do the config mapping automatically to let users set CASC_JENKINS_CONFIG themselves and point it to a folder of their choosing just like they could if it wasn't a helm chart

CASC_JENKINS_CONFIG