dependabot[bot] on maven
@bop0hz It looks fine. I suggest reporting a bug to JCasC.
atomic??????????tmpsuggests it is the atomic move operation in the Jenkins core. I am not 100% why jenkins_home is used as a temprary dir for that particular move (stacktrace won't show the cause), but JCasC should be robust against such race conditions in file operations
@oleg-nenashev thanks, are there any workarounds, how do you think?
ENV CASC_JENKINS_CONFIG /var/jenkins_home/. But container becomes stabilized and... it loads JCasC... from where? I went to the docs and found it:
If you do not set the CASC_JENKINS_CONFIG environment variable, the plugin will default to looking for a single config file in $JENKINS_ROOT/jenkins.yaml.Maybe it is a reason of race condition JCasC tries to load config twice?
The stable/jenkins helm chart. Already has support for the configuration as code plugin. It's possible to enable by setting
true. It also has support for automatically reloading any configuration change without restarting Jenkins. This is done via a sidecar container which watches for config map changes which contain the configuration (
master.sidecars.configAutoReload.enabled). You can also supply your JCasC configuration files via
That's all good to have, but I think the JCasC support could be improved even more. I just created an issue with a proposal in that regards: helm/charts#16931. I would love to here your feedback. If you want you can also support it by creating PRs which add better JCasC support.