config.xml, moved or renamed jobs via CLI, or updated your Jenkins home directory externally.
When to Use “Reload Configuration from Disk”
Use this feature to apply external changes immediately:| Scenario | Description | Command / UI Path |
|---|---|---|
Update config.xml | Edit system settings or messages | vi $JENKINS_HOME/config.xml |
| Rename or move jobs | Relocate job folders in the filesystem | mv $JENKINS_HOME/jobs/old-job $JENKINS_HOME/jobs/new-job |
| Adjust security or plugin configs | Change security realm, authorization strategy, or plugin files | N/A |
Reloading configuration does not apply plugin installations or upgrades. For plugin changes, use Manage Plugins and restart if required.
1. Update Configuration via the Jenkins UI
- Navigate to Dashboard → Manage Jenkins → Configure System.
- Find the System Message field.
- Enter a new message (e.g., “Welcome to KodeKloud”) and click Save.
- Verify the dashboard shows your updated system message.
2. Edit Configuration on the Filesystem
- SSH into your Jenkins server and switch to the Jenkins home directory:
- Open the main configuration file in your preferred editor:
- Locate the
<systemMessage>tag. Example before change: - Update it to your desired text:
- Save and exit the editor.
- Confirm the change:
Output should be:
3. Reload Configuration from Disk
- In Jenkins, go to Dashboard → Manage Jenkins.
- Scroll to Tools and Actions and click Reload Configuration from Disk.
- Confirm the prompt to proceed. Jenkins will re-import all configuration files.
Performing a reload can briefly impact running jobs. Avoid frequent reloads during peak build activity.
Benefits of Reloading from Disk
- Instant application of file-based edits
- No need for a full Jenkins restart
- Applies to jobs, system settings, security, and folder configurations