To manage Jenkins, go to the left-hand menu and select 'Manage Jenkins.'
So, from the left-hand menu, pick the 'Manage Jenkins' option to access the many setup choices for Jenkins.
The below screen will follow:
Given below are Jenkins management options −
Configure System
This is where you may configure the paths to the several tools that will be used in builds, such as JDKs, Maven, and Ant versions, as well as email servers, security options, and other system-wide setup details. After the plugins are installed, Jenkins will dynamically add the required configuration fields.
Reload Configuration from Disk
enkins stores all its system and build job configuration details as XML files which are stored in the Jenkins home directory. Here also, all of the build histories are stored. If you migrate build jobs from one Jenkins instance to another or archiving old build jobs, you will need to add or remove the corresponding build job directories to Jenkins’s builds directory. You don’t need to take Jenkins offline to do this—you can simply use the “Reload Configuration from Disk” option to reload the Jenkins system and build job configurations directly.
Jenkins saves all system and build job configuration information as XML files in the Jenkins home directory. All of the build history is likewise saved here. When moving build jobs from one Jenkins instance to another or archiving old build jobs, you must add or remove the necessary build job folders from Jenkins' builds directory. You don't have to take Jenkins offline to do this; simply utilise the "Reload Configuration from Disk" option to reload the Jenkins system and build job configurations.
Manage Plugin
From alternative source code management platforms like Git, ClearCase, or Mercurial to code quality and code coverage metrics reporting, one can install a wide range of third-party plugins here. The Manage Plugins tab allows you to install, update, and uninstall plugins.
System Information
This screen lists all of the current Java system characteristics and system environment variables. Here, you can see what version of Java Jenkins is running, what user it is running as, etc.
The screenshot below depicts some of the name-value information accessible in this section.
System Log
The System Log panel provides an easy method to view Jenkins log files in real-time. Again, the primary purpose of this panel is troubleshooting.
Load Statistics
This page shows graphical data on how busy the Jenkins instance is in terms of the number of concurrent builds and the length of the build queue, giving you a sense of how long your builds must wait before being done. This information can help determine whether additional capacity or construct nodes are required from an infrastructure standpoint.
Script Console
This screen allows you to execute Groovy scripts on the server. It is useful for advanced troubleshooting because it necessitates a thorough understanding of the Jenkins architecture.
Manage nodes
Jenkins can handle both parallel and distributed builds. You can specify how many builds you want on this screen. Jenkins runs concurrently, and if you're utilising distributed builds, you'll need to set up build nodes. A build node is an additional machine that Jenkins can use to run its builds.
