Build history and logs in Jenkins - Step-by-Step Execution

Process Flow - Build history and logs

Start Build

↓

Build Executes

↓

Log Output Generated

↓

Build Completes

↓

Store Build Result & Logs

↓

User Views Build History & Logs

↓

Analyze Success/Failure & Details

This flow shows how a Jenkins build runs, generates logs, stores results, and how users access the build history and logs.

Execution Sample

Jenkins

1. Trigger Jenkins build
2. Build runs and outputs logs
3. Build finishes with status
4. Logs and status saved
5. User views build history and logs

This sequence shows the steps from starting a build to viewing its history and logs in Jenkins.

Process Table

Step	Action	Build Status	Log Output	User View
1	Build triggered	N/A	No logs yet	Build not listed yet
2	Build running	In Progress	Logs streaming live	Build shows as running
3	Build completes	Success	Full logs saved	Build shows as Success
4	Logs stored	Success	Logs stored in Jenkins	Logs accessible in build history
5	User views history	Success	Logs displayed on UI	User sees build details and logs
6	New build triggered	N/A	No logs yet	New build appears in history

💡 Build completes and logs are saved; user can view build history and logs anytime.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5
Build Status	N/A	In Progress	Success	Success	Success
Log Output	No logs	Streaming logs	Full logs saved	Stored logs	Displayed logs
User View	No build	Build running	Build success	Logs accessible	Logs viewed

Key Moments - 3 Insights

Why does the build status show 'In Progress' before completion?

Because during step 2 in the execution_table, the build is running and logs are streaming live, so Jenkins marks the status as 'In Progress' until the build finishes.

How can users see logs if the build is still running?

At step 2, logs are streamed live, so users can view partial logs even before the build finishes, as shown in the 'Log Output' and 'User View' columns.

What happens to logs after the build completes?

After step 3 and 4, logs are fully saved and stored in Jenkins, making them accessible anytime in the build history, as shown in the 'Log Output' and 'User View' columns.

Visual Quiz - 3 Questions

Look at the execution_table, what is the build status at step 3?

A Success

B In Progress

C Failed

D Not Started

💡 Hint

Check the 'Build Status' column at step 3 in the execution_table.

At which step does the user first see the build logs?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the 'User View' and 'Log Output' columns in the execution_table to find when logs start streaming.

If the build fails at step 3, how would the 'Build Status' change in the variable_tracker?

A It would show 'In Progress'

B It would remain 'Success'

C It would change to 'Failed'

D It would be 'N/A'

💡 Hint

Refer to the 'Build Status' row in variable_tracker and consider what happens when a build fails.

Concept Snapshot

Jenkins Build History & Logs:
- Build starts and runs, generating logs live
- Logs and status saved after build completes
- Users access build history to see past builds
- Logs help analyze success or failure
- History shows build status and details

Full Transcript

In Jenkins, when you start a build, it runs and creates logs as it goes. The build status shows as 'In Progress' while running. Once finished, Jenkins saves the logs and marks the build as 'Success' or 'Failed'. Users can then view the build history and logs anytime to check what happened. Logs are streamed live during the build, so you can watch progress. This helps you understand if your build worked or if there were errors.

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