📖 Scenario: You are setting up a new Jenkins server for your team. Jenkins needs an initial admin user to secure the server and allow access to the dashboard.This project will guide you through creating the initial admin user setup using Jenkins configuration files.
🎯 Goal: Create the initial admin user configuration for Jenkins by defining the admin username and password in the configuration file, then verify the setup by printing the admin username.
📋 What You'll Learn
Create a Jenkins configuration dictionary with admin user details
Add a password configuration variable
Write a function to check if the admin user is set up correctly
Print the admin username to confirm the setup
💡 Why This Matters
🌍 Real World
Setting up Jenkins securely requires creating an initial admin user with a strong password to protect the server from unauthorized access.
💼 Career
DevOps engineers often configure Jenkins and other CI/CD tools to automate software delivery pipelines while ensuring security best practices.
Progress0 / 4 steps
1
Create Jenkins admin user configuration
Create a dictionary called jenkins_config with these exact entries: 'admin_user': 'admin' and 'admin_password': 'changeme'.
Jenkins
Hint
Use a Python dictionary with keys 'admin_user' and 'admin_password'.
2
Add password complexity requirement
Create a variable called password_min_length and set it to 8 to represent the minimum password length requirement.
Jenkins
Hint
Just create a variable with the exact name and value.
3
Check admin password length
Write a function called is_password_valid that takes no arguments and returns True if the length of jenkins_config['admin_password'] is greater than or equal to password_min_length, otherwise returns False.
Jenkins
Hint
Define a function with no parameters that checks the password length.
4
Print admin username if password is valid
Write a print statement that prints jenkins_config['admin_user'] only if is_password_valid() returns True. Otherwise, print 'Password too short'.
Jenkins
Hint
Use an if-else statement to print the admin username or an error message.
Practice
(1/5)
1. What is the main purpose of the Jenkins initial admin setup wizard?
easy
A. To deploy Jenkins jobs automatically
B. To configure Jenkins system settings like memory and CPU usage
C. To guide users through installing plugins and creating the first admin user
D. To backup Jenkins data to the cloud
Solution
Step 1: Understand the wizard's role
The initial admin setup wizard helps new Jenkins users start quickly by guiding them through essential setup steps.
Step 2: Identify key tasks of the wizard
It installs recommended plugins and creates the first admin user to secure Jenkins access.
Final Answer:
To guide users through installing plugins and creating the first admin user -> Option C
Quick Check:
Wizard purpose = guide setup [OK]
Hint: Wizard sets up plugins and admin user first [OK]
Common Mistakes:
Thinking it configures system resources
Assuming it deploys jobs automatically
Believing it handles backups
2. Which of the following commands is used to unlock Jenkins during the initial admin setup?
easy
A. cat /var/lib/jenkins/secrets/initialAdminPassword
B. jenkins unlock --start
C. sudo service jenkins unlock
D. unlock-jenkins --password
Solution
Step 1: Identify the unlock method
Jenkins stores the initial admin password in a file named initialAdminPassword inside the secrets directory.
Step 2: Use the correct command to read the password
The cat command displays the password content to unlock Jenkins.
Final Answer:
cat /var/lib/jenkins/secrets/initialAdminPassword -> Option A
Quick Check:
Unlock command = cat password file [OK]
Hint: Use cat on initialAdminPassword file to unlock [OK]
Common Mistakes:
Using non-existent Jenkins unlock commands
Trying to unlock via service commands
Confusing unlock with start or restart commands
3. After completing the initial admin setup wizard, what will Jenkins display when you access the dashboard for the first time?
medium
A. A prompt to create a new admin user
B. The Jenkins dashboard with default plugins installed
C. An error message about missing plugins
D. A blank page with no content
Solution
Step 1: Understand wizard completion effects
Completing the wizard installs recommended plugins and sets up the admin user.
Step 2: Identify the dashboard state after setup
Jenkins shows the dashboard with default plugins ready for use, not an error or blank page.
Final Answer:
The Jenkins dashboard with default plugins installed -> Option B
Quick Check:
Dashboard after setup = plugins installed [OK]
Hint: Dashboard shows plugins after setup wizard completes [OK]
Common Mistakes:
Expecting a prompt to create admin again
Thinking an error appears about plugins
Assuming the page is blank initially
4. You ran the initial admin setup wizard but Jenkins still asks for the unlock password repeatedly. What is the most likely cause?
medium
A. The initialAdminPassword file was deleted or inaccessible
B. The Jenkins service is not running
C. The plugins failed to install
D. The admin user was created twice
Solution
Step 1: Identify why unlock repeats
Jenkins requires the initial admin password from the initialAdminPassword file to unlock.
Step 2: Understand impact of missing password file
If the file is deleted or unreadable, Jenkins cannot verify unlock and keeps asking for the password.
Final Answer:
The initialAdminPassword file was deleted or inaccessible -> Option A
Quick Check:
Unlock repeats if password file missing [OK]
Hint: Check if initialAdminPassword file exists and is readable [OK]
Common Mistakes:
Assuming Jenkins service stopped causes unlock loop
Blaming plugin installation failure for unlock issue
Thinking duplicate admin users cause unlock prompt
5. You want to automate Jenkins initial setup without manual unlock. Which approach correctly achieves this?
hard
A. Pre-create the initialAdminPassword file with a known password before Jenkins starts
B. Install Jenkins plugins manually after first login
C. Use Jenkins CLI to skip the unlock step after startup
D. Disable the initial admin setup wizard in Jenkins configuration files
Solution
Step 1: Understand automation goal
To avoid manual unlock, the initial setup wizard must be disabled or bypassed.
Step 2: Identify correct method
Disabling the wizard in Jenkins configuration allows automated startup without unlock prompts.
Step 3: Evaluate other options
Pre-creating password file is insecure and unreliable; CLI cannot skip unlock; manual plugin install is after unlock.
Final Answer:
Disable the initial admin setup wizard in Jenkins configuration files -> Option D
Quick Check:
Disable wizard to automate setup [OK]
Hint: Disable wizard in config to skip manual unlock [OK]
Common Mistakes:
Trying to pre-create password file manually
Assuming CLI can skip unlock step
Thinking manual plugin install automates unlock
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.