instruction: Show me how to configure jenkins for CI/CD automation
output: Traditionally, experienced Jenkins administrators
  created Apache Groovy init scripts
  to automate the configuration for their Jenkins controllers.
  This works but requires in-depth understanding of Jenkins APIs
  and the ability to write Groovy scripts.
  Such scripts are powerful and can do almost anything,
  but they also provide few protections against configuration errors.
  The Configuration as Code UI page shows the full pathname of the YAML file being used
  and gives a box where you can specify a different file to use.
  See the information below about how to modify the location used for JCasC YAML files.
  jenkins : systemMessage : " Jenkins configured automatically by Jenkins Configuration as Code plugin \n\n "
  It is not necessary to restart Jenkins to apply the JCasC changes,
  although you should try to restart Jenkins with the modifications
  before you check the modified YAML file into SCM,
  especially when making more substantive configuration changes.
  [Service]
  Environment="JAVA_OPTS=-Dcasc.jenkins.config=/jenkins/casc_configs"