instruction: Show me how to configure jenkins for CI/CD automation
output: JENKINS_HOME
   +- builds (build records)
   +- [BUILD_ID] (subdirectory for each build)
   +- build.xml (build result summary)
   +- changelog.xml (change log)
   +- config.xml (Jenkins root configuration file)
   +- *.xml (other site-wide configuration files)
   +- fingerprints (stores fingerprint records, if any)
   +- identity.key.enc (RSA key pair that identifies an instance)
   +- jobs (root directory for all Jenkins jobs)
   +- [JOBNAME] (sub directory for each job)
   +- config.xml (job configuration file)
   +- [FOLDERNAME] (sub directory for each folder)
   +- config.xml (folder configuration file)
   +- jobs (subdirectory for all nested jobs)
   +- plugins (root directory for all Jenkins plugins)
   +- [PLUGIN] (sub directory for each plugin)
   +- [PLUGIN].jpi (.jpi or .hpi file for the plugin)
   +- secret.key (deprecated key used for some plugins' secure operations)
   +- secret.key.not-so-secret (used for validating _$JENKINS_HOME_ creation date)
   +- secrets (root directory for the secret+key for credential decryption)
   +- hudson.util.Secret (used for encrypting some Jenkins data)
   +- master.key (used for encrypting the hudson.util.Secret key)
   +- InstanceIdentity.KEY (used to identity this instance)
   +- jenkins.model.Jenkins.crumbSalt (used for encrypting some Jenkins data)
   +- initialAdminPassword (used for initial login)
   +- userContent (files served under your https://server/userContent/)
   +- workspace (working directory for the version control system)
  JENKINS_HOME
   +- builds (build records)
   +- [BUILD_ID] (subdirectory for each build)
   +- build.xml (build result summary)
   +- changelog.xml (change log)
   +- config.xml (Jenkins root configuration file)
   +- *.xml (other site-wide configuration files)
   +- fingerprints (stores fingerprint records, if any)
   +- identity.key.enc (RSA key pair that identifies an instance)
   +- jobs (root directory for all Jenkins jobs)
   +- [JOBNAME] (sub directory for each job)
   +- config.xml (job configuration file)
   +- [FOLDERNAME] (sub directory for each folder)
   +- config.xml (folder configuration file)
   +- jobs (subdirectory for all nested jobs)
   +- plugins (root directory for all Jenkins plugins)
   +- [PLUGIN] (sub directory for each plugin)
   +- [PLUGIN].jpi (.jpi or .hpi file for the plugin)
   +- secret.key (deprecated key used for some plugins' secure operations)
   +- secret.key.not-so-secret (used for validating _$JENKINS_HOME_ creation date)
   +- secrets (root directory for the secret+key for credential decryption)
   +- hudson.util.Secret (used for encrypting some Jenkins data)
   +- master.key (used for encrypting the hudson.util.Secret key)
   +- InstanceIdentity.KEY (used to identity this instance)
   +- jenkins.model.Jenkins.crumbSalt (used for encrypting some Jenkins data)
   +- initialAdminPassword (used for initial login)
   +- userContent (files served under your https://server/userContent/)
   +- workspace (working directory for the version control system)
  The system is undergoing maintenance on YYYY-MM-DD.
  Expect downtime.
  Why set executors to 0 on the controller? Setting executors to 0 ensures that the controller is dedicated to managing builds and coordinating agents, rather than executing builds itself.
  This improves stability and performance. For instance, agents with specific capabilities can be configured with multiple executors to handle concurrent builds effectively.
  linux, windows, docker, high-memory
  Set a quiet period of 5 seconds to batch changes.
  For detailed instructions on configuring a reverse proxy, refer to the reverse proxy configuration guide.
  Tip: Use the question mark ( ? ) icon next to each setting to access detailed help for that specific configuration.