Skip to main content
In this lesson, we explore the key sections under Manage Jenkins → Configure System. You’ll learn how to adjust node parameters, set your Jenkins URL, and specify the system administrator email for notifications.

​
Node Configuration

On the Configure System page, the primary node settings include:
SettingDescriptionDefault/Example
Home directoryFilesystem path where Jenkins stores all data/var/jenkins_home
System messageCustom text displayed at the top of the dashboard—
Number of executorsHow many concurrent builds this node can run2
LabelsIdentifiers for targeting this node in jobsnone
UsageScheduling policy (e.g., “Use this node as much as possible”)Use this node as much as possible
The image shows a Jenkins system configuration page in a web browser, with options for setting the number of executors, usage preferences, and other settings.
You can enforce naming conventions by defining patterns under the Item naming section. This practice improves consistency across jobs.

​
Jenkins Location

Accurately setting the Jenkins URL is critical for links, webhooks, and notifications. Keep these best practices in mind:
  • Choose a memorable hostname, for example, jenkins.example.com.
  • Always use HTTPS to secure traffic.
  • Avoid exposing internal hostnames or overly complex domains.
Configuring localhost as your Jenkins URL in production will trigger warnings and prevent external integrations from working correctly.
The image shows a Jenkins system configuration page in a web browser, where the Jenkins URL is being set, and a warning message indicates the need for a valid host name instead of "localhost."
In this local demo, we’ll revert to: 
http://localhost:8080
but be sure to replace it with your HTTPS address in a real deployment.

​
System Admin Email

Specify the system administrator’s email address to receive critical alerts and build-failure notifications. This field integrates with your email notification settings, ensuring you’re alerted to issues in real time.

Watch Video