Build history and logs in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of build history in Jenkins?

Build history in Jenkins keeps a record of all past builds, showing their status, duration, and time. It helps track what happened in each build over time.

beginner

Where can you find the logs for a specific Jenkins build?

You can find the logs by clicking on the build number in the build history, then selecting 'Console Output'. This shows detailed steps and messages from that build.

beginner

What information does the Jenkins console output provide?

The console output shows step-by-step messages, errors, warnings, and success messages from the build process. It helps diagnose problems or confirm success.

intermediate

How can build history help in troubleshooting Jenkins jobs?

Build history shows which builds failed or succeeded and when. By reviewing logs from failed builds, you can find errors and fix issues faster.

intermediate

What happens to build logs when Jenkins is configured to discard old builds?

When old builds are discarded, their logs and details are deleted to save space. Only recent builds remain accessible in the build history.

Where do you click to see the logs of a Jenkins build?

A On the build number in the build history

B On the Jenkins dashboard logo

C On the system settings

D On the user profile

Clicking the build number in the build history opens details including the console output logs.

What does the Jenkins console output NOT show?

A User login history

B Errors and warnings

C Step-by-step build messages

D Success messages

Console output shows build details, not user login history.

Why is build history important in Jenkins?

A To add new users

B To change Jenkins system settings

C To edit source code

D To track past build results and durations

Build history helps track what happened in previous builds.

What happens if Jenkins is set to discard old builds?

A Build history is duplicated

B Old build logs are deleted

C New builds are ignored

D Builds run faster

Discarding old builds deletes their logs to save space.

How can you use build logs to fix a failed Jenkins job?

A By deleting the job

B By restarting Jenkins server

C By reading error messages in the console output

D By changing user permissions

Error messages in logs help identify what went wrong.

Explain how Jenkins build history and logs help in managing and troubleshooting builds.

Think about how you would check what happened if a build failed.

Describe what happens to build logs when Jenkins discards old builds and why this might be useful.

Consider storage limits and system performance.