Jenkins home directory structure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the purpose of the 'jobs' directory in Jenkins home

In the Jenkins home directory, what is the main purpose of the jobs folder?

A It holds plugin binaries and their configurations

B It contains Jenkins system logs and error reports

C It stores configuration and build history for each Jenkins job

D It stores user credentials and security settings

💡 Hint

Think about where Jenkins keeps information about individual projects it builds.

The jobs directory contains folders for each Jenkins job. Each job folder holds configuration files and build history specific to that job.

💻 Command Output

intermediate

Output of listing Jenkins home directory contents

What is the typical output when running ls -1 inside a Jenkins home directory?

Jenkins

ls -1

A

tmp
cache
var
etc
opt

B

bin
lib
src
docs
tests

C

config.xml
build.xml
README.md
LICENSE

D

jobs
plugins
secrets
users
fingerprints
logs

💡 Hint

Focus on directories related to Jenkins job data, plugins, and user info.

The Jenkins home directory typically contains folders like jobs, plugins, secrets, users, fingerprints, and logs.

❓ Troubleshoot

advanced

Troubleshooting missing build history in Jenkins

You notice that Jenkins is not showing any build history for a job. Which Jenkins home directory issue is the most likely cause?

A The <code>jobs/job_name/builds</code> directory is missing or corrupted

B The <code>users</code> directory has incorrect permissions

C The <code>plugins</code> directory is empty

D The <code>workspace</code> directory is full of old files

💡 Hint

Build history is stored inside a specific subfolder of the job directory.

Build history is stored inside the builds folder within each job's directory. If this folder is missing or corrupted, Jenkins cannot show build history.

✅ Best Practice

advanced

Best practice for backing up Jenkins home directory

Which is the best practice for backing up the Jenkins home directory to ensure full recovery?

A Backup only the <code>jobs</code> directory since it contains job data

B Backup the entire Jenkins home directory including <code>jobs</code>, <code>plugins</code>, <code>secrets</code>, and <code>users</code> folders

C Backup only the <code>plugins</code> directory to preserve plugin data

D Backup only the <code>workspace</code> directory to save build artifacts

💡 Hint

Think about what is needed to restore Jenkins fully after failure.

Backing up the entire Jenkins home directory ensures all job configurations, plugins, user data, secrets, and build history are preserved for full recovery.

🔀 Workflow

expert

Order of steps to safely upgrade Jenkins plugins

Arrange the correct order of steps to safely upgrade Jenkins plugins using the Jenkins home directory.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 2,3,1,4

💡 Hint

Think about safety and minimizing downtime during plugin upgrades.

First backup to prevent data loss, then stop Jenkins to avoid conflicts, replace plugins safely, and finally start Jenkins to check everything works.