I have been doing a little research on the Jenkins Configuration as Code (JCasC) plugin and I must say I think it’s definitely a step in the right direction.
In theory, with this plugin, you can have the majority of your Jenkins configuration stored in 1 file. This file can then be put in source control, which would allow you to easily rebuild your Jenkins instance at anytime.
However, while playing around with the plugin, a couple things came to my mind.
- It was hard for me to determine the correct syntax that needed to go into my jenkins.yaml file. There are examples located here, but these weren’t enough for me to get moving quickly.
- Long term, it could be a bit cumbersome to make all changes in the yaml file correctly, then re-apply to Jenkins instances.
- If the examples and plugin mature more, this is surely a easy way for teams to fail-safe\share their Jenkins configuration
- Fixing or growing the jenkins.yaml export functionality would greatly help. This would essentially allow you to apply Jenkins changes manually, then export to see the correct yaml syntax.
Anyways – This is a cool plugin that I am surely looking forward to using in the future!