Build history and logs in Jenkins - Mini Project: Build & Apply

Build history and logs

📖 Scenario: You are setting up a Jenkins job to keep track of build history and logs. This helps you see which builds succeeded or failed and review their logs for troubleshooting.

🎯 Goal: Create a Jenkins pipeline script that stores build results and logs in a dictionary, then prints the build history summary.

📋 What You'll Learn

Create a dictionary called build_history with build numbers as keys and their status as values.

Add a variable called latest_build to store the most recent build number.

Use a for loop to collect build logs for each build number in build_history.

Print the build history summary showing build numbers, status, and logs.

💡 Why This Matters

🌍 Real World

Jenkins pipelines keep track of build results and logs to help developers quickly see what happened in each build and troubleshoot failures.

💼 Career

Understanding how to manage build history and logs is essential for DevOps engineers and CI/CD pipeline maintainers to ensure software quality and fast issue resolution.

1

Create initial build history dictionary

Create a dictionary called build_history with these exact entries: 1: 'SUCCESS', 2: 'FAILURE', 3: 'SUCCESS'.

Jenkins

# Create the build_history dictionary with build numbers and statuses
# Your code here

Hint

Use curly braces to create a dictionary with keys 1, 2, 3 and their status values.

2

Add latest build number variable

Add a variable called latest_build and set it to 3.

Jenkins

build_history = {1: 'SUCCESS', 2: 'FAILURE', 3: 'SUCCESS'}
# Add latest_build variable with value 3
# Your code here

Hint

Just assign the number 3 to the variable latest_build.

3

Collect build logs in a dictionary

Create an empty dictionary called build_logs. Use a for loop with variable build_num to iterate over build_history.keys(). Inside the loop, add an entry to build_logs with key build_num and value f'Log for build {build_num}'.

Jenkins

build_history = {1: 'SUCCESS', 2: 'FAILURE', 3: 'SUCCESS'}
latest_build = 3
# Create build_logs dictionary and fill it with logs for each build
# Your code here

Hint

Use a for loop over build_history.keys() and assign formatted strings to build_logs dictionary.

4

Print build history summary

Use a for loop with variables build_num and status to iterate over build_history.items(). Inside the loop, print the line exactly as: Build {build_num}: Status={status}, Log={build_logs[build_num]}.

Jenkins

build_history = {1: 'SUCCESS', 2: 'FAILURE', 3: 'SUCCESS'}
latest_build = 3
build_logs = {}
for build_num in build_history.keys():
    build_logs[build_num] = f'Log for build {build_num}'
# Print build summary lines below
# Your code here

Hint

Use a for loop over build_history.items() and print the formatted string with build number, status, and log.

Practice

1. What does the Build History section in Jenkins primarily show?

easy

A. The configuration settings of the Jenkins server

B. The detailed logs of the current build

C. A list of past builds with their results and status

D. The list of users who accessed Jenkins

Solution

1. Step 1: Understand the purpose of Build History

   The Build History section shows a timeline of previous builds with their success or failure status.

2. Step 2: Differentiate from build logs and settings

   Build logs show detailed steps, not the summary list. Configuration and user lists are separate sections.

3. Final Answer:

   A list of past builds with their results and status -> Option C

4. Quick Check:

   Build History = past build results [OK]

Hint: Build History = summary of past builds, not logs [OK]

Common Mistakes:

• Confusing Build History with build logs
• Thinking Build History shows Jenkins settings
• Assuming Build History lists users

2. Which Jenkins UI element do you click to view the detailed logs of a specific build?

easy

A. The build number link in Build History

B. The 'Configure' button on the job page

C. The 'New Item' button on the dashboard

D. The 'Manage Jenkins' link

Solution

1. Step 1: Identify where build logs are accessed

   Clicking the build number in Build History opens that build's details including logs.

2. Step 2: Exclude unrelated UI elements

   'Configure' edits job settings, 'New Item' creates jobs, 'Manage Jenkins' is for admin tasks.

3. Final Answer:

   The build number link in Build History -> Option A

4. Quick Check:

   Build logs accessed via build number link [OK]

Hint: Click build number in history to see logs [OK]

Common Mistakes:

• Clicking 'Configure' instead of build number
• Trying 'New Item' to see logs
• Using 'Manage Jenkins' for build logs

3. Given a Jenkins job with three builds: #1 (SUCCESS), #2 (FAILURE), #3 (SUCCESS). What will the Build History show after build #3 completes?

medium

A. Build #3 FAILURE, Build #2 SUCCESS, Build #1 FAILURE

B. Build #1 SUCCESS, Build #2 FAILURE, Build #3 SUCCESS

C. Build #2 FAILURE only

D. Build #3 SUCCESS, Build #2 FAILURE, Build #1 SUCCESS

Solution

1. Step 1: Understand Build History order

   Build History lists builds in reverse order: newest first.

2. Step 2: Match build statuses and order

   Build #3 is latest and successful, then #2 failed, then #1 successful.

3. Final Answer:

   Build #3 SUCCESS, Build #2 FAILURE, Build #1 SUCCESS -> Option D

4. Quick Check:

   Newest builds appear first in history [OK]

Hint: Build History shows newest builds first [OK]

Common Mistakes:

• Reading builds oldest to newest
• Mixing up build statuses
• Assuming only failed builds show

4. You try to view build logs but see an empty page. What is the most likely cause?

medium

A. You clicked the wrong build number

B. The build has not started or produced logs yet

C. Jenkins server is offline

D. You lack permission to view logs

Solution

1. Step 1: Consider build status and logs availability

   If the build is queued or just started, logs may be empty.

2. Step 2: Exclude other causes

   Wrong build number still shows logs if build exists; server offline shows error; permission issues show access denied.

3. Final Answer:

   The build has not started or produced logs yet -> Option B

4. Quick Check:

   Empty logs usually mean build not started [OK]

Hint: Empty logs = build not started or no output yet [OK]

Common Mistakes:

• Assuming server offline causes empty logs
• Thinking wrong build number shows empty logs
• Ignoring permission errors

5. You want to analyze why a Jenkins build failed by checking logs but the logs are very long. Which Jenkins feature helps you quickly find errors in the logs?

hard

A. The 'Console Output' search box to filter keywords

B. The 'Build History' to rerun the build

C. The 'Configure' page to edit build steps

D. The 'Manage Jenkins' to restart the server

Solution

1. Step 1: Identify how to search logs

   Jenkins Console Output page often has a search/filter box to find keywords like 'error'.

2. Step 2: Exclude unrelated features

   Build History shows past builds but no search; Configure edits jobs; Manage Jenkins is for admin tasks.

3. Final Answer:

   The 'Console Output' search box to filter keywords -> Option A

4. Quick Check:

   Use Console Output search to find errors fast [OK]

Hint: Use Console Output search box to find errors fast [OK]

Common Mistakes:

• Trying to find errors via Build History
• Editing job instead of checking logs
• Restarting Jenkins unnecessarily