Admin for Jenkinss
Jenkins administration is the configuration of the controller through Manage Jenkins: global tool settings, system configuration, credentials, nodes, plugin management and Configuration as Code. This unit in the Managing Jenkins stage focuses on keeping a server consistent, reproducible and easy to rebuild.
Stage: Managing Jenkins · Part of the Jenkins roadmap · Last reviewed 19 November 2026
What to learn in Admin
- Configure global tools such as JDK, Maven and Git in Manage Jenkins
- Store secrets as credentials and bind them inside a pipeline
- Describe system settings in a YAML file using Configuration as Code
- Review plugin updates and plan safe upgrade steps
- Locate JENKINS_HOME and explain what it contains
Admin interview questions
What is JENKINS_HOME and why does it matter?
JENKINS_HOME is the directory where Jenkins stores configuration, job definitions, build history, credentials and installed plugins. Backing it up captures the whole server state, and keeping it on persistent storage is essential when running Jenkins in a container.
What is Jenkins Configuration as Code?
Configuration as Code, or JCasC, is a plugin that lets you describe controller settings such as security, nodes and credentials in a YAML file. The file is applied at startup, so a Jenkins instance can be rebuilt identically and changes can be reviewed in Git.
Where Admin fits in the Jenkins roadmap
Admin belongs to the Managing Jenkins stage (intermediate level). Configuration.
Other units in this stage
Back to the full Jenkins roadmap