Build history and logs in Jenkins - Commands & Configuration

Introduction

When you run a Jenkins job, it keeps a record of each build and its logs. This helps you see what happened during each run and find problems if the build fails.

When you want to check if a recent build succeeded or failed.

When you need to find errors or warnings from a build to fix issues.

When you want to compare the results of different builds over time.

When you want to audit who triggered a build and when.

When you want to download or share build logs with your team.

Commands

This command lists the build history for the Jenkins job named 'my-job'. It shows build numbers and their status.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080 list-builds my-job

Expected Output

Build #5 SUCCESS

Build #4 FAILURE

Build #3 SUCCESS

Build #2 SUCCESS

Build #1 FAILURE

→

-s - Specifies the Jenkins server URL

This command shows the console log output of build number 5 for the job 'my-job'. It helps you see what happened during that build.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080 console my-job 5

Expected Output

[Pipeline] Start of Pipeline

[Pipeline] echo

Building project

[Pipeline] sh

+ mvn clean install

[INFO] BUILD SUCCESS

[Pipeline] End of Pipeline

→

-s - Specifies the Jenkins server URL

This command triggers a new build of the job 'my-job' and waits for it to finish. Useful to start a build from the command line.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080 build my-job -w

Expected Output

Started build #6

Finished build #6 SUCCESS

→

-w - Waits until the build completes before returning

This command downloads the job configuration XML file for 'my-job'. It can be used to backup or inspect job settings.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080 get-job my-job > my-job-config.xml

Expected Output

No output (command runs silently)

→

-s - Specifies the Jenkins server URL

Key Concept

If you remember nothing else from this pattern, remember: Jenkins keeps every build's details and logs so you can track and troubleshoot your jobs easily.

Common Mistakes

Trying to view build logs without specifying the correct build number.

Jenkins needs the exact build number to show logs; otherwise, it cannot find which build's logs to display.

Always specify the build number when requesting logs, for example: 'console my-job 5'.

Not using the Jenkins CLI with the correct server URL.

The CLI commands fail if they don't know which Jenkins server to connect to.

Always include the '-s http://localhost:8080' flag or your Jenkins server URL.

Assuming the build command triggers a build instantly without waiting.

Without the '-w' flag, the build command triggers the build but returns immediately, so you don't know when it finishes.

Use the '-w' flag to wait for the build to complete and get the result.

Summary

Use Jenkins CLI commands to list builds and see their status.

View detailed logs of any build by specifying the job name and build number.

Trigger new builds from the command line and wait for their completion.

Download job configuration files for backup or inspection.

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