HTML reports publishing in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins HTML Publisher Plugin Basic Usage

You have configured the Jenkins HTML Publisher plugin to publish reports from the directory target/reports with the report name Test Report. After a successful build, what will be the URL path to access this report in Jenkins?

A /job/<job-name>/lastSuccessfulBuild/htmlreports/Test%20Report/index.html

B /job/<job-name>/lastSuccessfulBuild/htmlreports/Test Report/index.html

C /job/<job-name>/lastSuccessfulBuild/htmlreports/Test_Report/index.html

D /job/<job-name>/lastSuccessfulBuild/artifact/target/reports/index.html

💡 Hint

Spaces in report names are encoded in URLs.

The HTML Publisher plugin encodes spaces as %20 in URLs. The report is accessible under the htmlreports path with the report name as folder, so spaces become %20.

❓ Configuration

intermediate

Correct Jenkins Pipeline Syntax for HTML Report Publishing

Which Jenkins pipeline snippet correctly publishes HTML reports located in build/reports with the report name Coverage Report?

A publishHTML([allowMissing: false, alwaysLinkToLastBuild: true, keepAll: true, reportDir: 'build/reports', reportFiles: 'index.html', reportName: 'Coverage Report'])

B publishHTML(reportDir: 'build/reports', reportFiles: 'index.html', reportName: 'Coverage Report')

C publishHTML([reportDir: 'build/reports', reportFiles: 'index.html', reportName: 'Coverage Report'])

D publishHTML('build/reports', 'index.html', 'Coverage Report')

💡 Hint

The publishHTML step requires a map inside a list with specific keys.

The publishHTML step expects a list of maps with keys like reportDir, reportFiles, reportName, and optional flags. Option A correctly uses this syntax.

❓ Troubleshoot

advanced

Troubleshooting Missing HTML Reports in Jenkins

After configuring the HTML Publisher plugin, the reports do not appear in Jenkins UI. Which of the following is the most likely cause?

A The Jenkins user does not have permission to access the Jenkins UI.

B The Jenkins server is missing the HTML Publisher plugin installation.

C The reportFiles parameter is set to a file that is not an HTML file.

D The report directory path is incorrect or does not exist at build time.

💡 Hint

Check the build workspace for the report directory existence.

If the report directory does not exist or is empty at the time of publishing, the reports will not show. Permissions or plugin absence would cause different errors.

🔀 Workflow

advanced

Order of Steps to Publish HTML Reports in Jenkins Pipeline

Arrange the following Jenkins pipeline steps in the correct order to generate and publish HTML reports:

A 1,2,3,4

B 1,3,2,4

C 3,1,2,4

D 3,2,1,4

💡 Hint

Source code must be checked out before tests run.

First checkout code (3), then run tests to generate reports (1), then publish reports (2), and optionally archive artifacts (4).

✅ Best Practice

expert

Best Practice for Handling Spaces in HTML Report Names in Jenkins

You want to publish multiple HTML reports with names containing spaces, such as Test Report and Coverage Report. What is the best practice to avoid URL and access issues?

A Use spaces as is; Jenkins automatically handles encoding.

B Replace spaces with underscores in report names before publishing.

C Use only lowercase letters and no spaces in report names.

D Publish reports without specifying report names to avoid spaces.

💡 Hint

Spaces in URLs can cause encoding issues.

Replacing spaces with underscores avoids URL encoding problems and makes URLs cleaner and easier to access.