Recently set up an experimental Jenkins CASC server and it is very promising so we have decided to try it out in production.
The only issue I have is that it seems like Job DSL is THE way to handle the job configurations, either by using Organization Folders or by loading up Job DSL groovy scripts that include the job configuration parts that can not be applied to the Jenkinsfiles.
I see that Job DSL is up for adoption, how much of a red flag is that? Or does it simply mean that they need more hands, but it is being maintained?