Operations 3 min read

Step‑by‑Step Guide to Installing and Configuring Jenkins on Linux

This article provides a comprehensive, step‑by‑step tutorial for installing, configuring, and running Jenkins on a Linux server, covering environment preparation, Java installation, Jenkins deployment, initial password retrieval, plugin sources, and basic configuration.

Practical DevOps Architecture
Practical DevOps Architecture
Practical DevOps Architecture
Step‑by‑Step Guide to Installing and Configuring Jenkins on Linux

Jenkins is an open‑source automation server that provides an easy‑to‑use continuous integration system, freeing developers from complex integration tasks and allowing them to focus on core business logic. It can monitor builds in real time, generate detailed logs, send alerts, and display build trends and stability via charts.

Jenkins can create an automated CI environment that “automates” compiling, packaging, and deploying applications; it integrates with build tools such as Ant, Maven, Gradle, works with version‑control systems like SVN and Git, and can directly connect to popular code‑hosting platforms such as GitHub and Bitbucket.

1. Initialize the system environment – disable the firewall and SELinux.

2. Configure YUM repositories.

3. Install the Java runtime. yum install java-1.8.0-openjdk java-1.8.0-openjdk-devel -y Verify the installation:

java -version

4. Install Jenkins by downloading the WAR file from the official mirror.

Download address: https://mirrors.tuna.tsinghua.edu.cn/jenkins/war-stable

5. Run Jenkins:

nohup java -jar jenkins.2.222.3.war > /tmp/jenkins.out 2>&1 &

6. Retrieve the initial admin password: more /root/.jenkins/secrets/initialAdminPassword 7. Log in to the Jenkins web UI.

Jenkins plugin repositories – international: https://updates.jenkins-ci.org/download/plugins; domestic (China): https://mirrors.tuna.tsinghua.edu.cn/jenkins/plugins.

Remember to change the default admin password after the first login.

Basic Jenkins Configuration

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

ci/cdAutomationDevOpslinuxcontinuous integrationJenkins
Practical DevOps Architecture
Written by

Practical DevOps Architecture

Hands‑on DevOps operations using Docker, K8s, Jenkins, and Ansible—empowering ops professionals to grow together through sharing, discussion, knowledge consolidation, and continuous improvement.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.