Manage Jenkins
Configure global settings and paths. | |
Secure Jenkins; define who is allowed to access/use the system. | |
Configure the credential providers and types | |
Configure tools, their locations and automatic installers. | |
Discard all the loaded data in memory and reload everything from file system.
Useful when you modified config files directly on disk. | |
Add, remove, disable or enable plugins that can extend the functionality of Jenkins. (updates available) | |
Displays various environmental information to assist trouble-shooting. | |
System log captures output from java.util.logging output related to Jenkins. | |
Check your resource utilization and see if you need more computers for your builds. | |
Access/manage Jenkins from your shell, or from your script. | |
Executes arbitrary script for administration/trouble-shooting/diagnostics. | |
Add, remove, control and monitor the various nodes that Jenkins runs jobs on. | |
Handle permissions by creating roles and assigning them to users/groups | |
Configure a single aspect across a group of items, in contrast to the traditional configuration of all aspects of a single item | |
See the version and license information. | |
Scrub configuration files to remove remnants from old plugins and earlier versions. | |
Restart once no jobs are running. | |
e.g. settings.xml for maven, central managed scripts, custom files, ... | |
Configure global templates for Editable Email Notification Plugin | |
Store/edit/run scripts on any of the slaves or the master. | |
Allows a Jenkins administrator to review proposed scripts (written e.g. in Groovy) which run inside the Jenkins process and so could bypass security restrictions. | |
Monitoring of memory, cpu, http requests and more in Jenkins master. You can also view the monitoring of Jenkins nodes. | |
Stops executing new builds, so that the system can be eventually shut down safely. |