Installation and Setup

Installation and Setup

Jenkins requires a supported Java runtime and persistent JENKINS_HOME. It can run from a native package, WAR file, container, or managed platform. Production choice depends on operating expertise, backup strategy, upgrade process, and agent architecture—not just the quickest installation.

Core ideas

• The LTS line emphasizes stability; read upgrade guides before changing Jenkins core or Java versions.
• JENKINS_HOME contains job definitions, plugin data, secrets, build records, and system configuration.
• The setup wizard unlocks the instance, creates an administrator, and selects initial plugins.
• A reverse proxy commonly terminates TLS and forwards requests with correct host and scheme headers.

How it works

Start with a supported Java version, stable DNS, TLS, durable storage, restricted network access, and an explicit service account. Create named administrators instead of sharing credentials. Configure the Jenkins URL, email, security realm, authorization, agents, and backup before onboarding critical pipelines.

Configuration example

# Ubuntu example: verify the supported Java runtime first
java -version
sudo systemctl enable --now jenkins
sudo systemctl status jenkins

# Protect and back up this directory according to your platform
sudo ls -ld /var/lib/jenkins

The sample is intentionally small. In a real installation, replace hostnames, labels, credentials, retention, and commands with reviewed values from your own platform standards.

Production guidance

• Never expose a fresh unauthenticated controller directly to the internet.
• Test core, Java, and plugin upgrades in a representative non-production environment.
• Back up configuration and secrets securely; validate restoration, not merely backup creation.

The chapter quiz follows this lesson and tests both terminology and safe operating choices.