Pipeline linting and validation in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of Jenkins pipeline lint command with a valid Jenkinsfile?

You run the Jenkins CLI command to lint a Jenkinsfile that has no syntax errors. What output do you expect?

Jenkins

java -jar jenkins-cli.jar -s http://jenkins.example.com/ lint-pipeline < Jenkinsfile

A Syntax error at line 3

B Jenkinsfile is valid

C Permission denied

D Unknown command

💡 Hint

Linting checks syntax without running the pipeline.

The lint-pipeline command checks the Jenkinsfile syntax and returns 'Jenkinsfile is valid' if no errors are found.

🧠 Conceptual

intermediate

Which Jenkins feature validates pipeline syntax before saving?

In Jenkins, which feature helps you check pipeline syntax before saving the Jenkinsfile in the UI?

A Blue Ocean Editor

B Pipeline Syntax Snippet Generator

C Declarative Pipeline Linter

D Script Security Plugin

💡 Hint

This feature checks the whole pipeline script syntax.

The Declarative Pipeline Linter validates the pipeline syntax before saving it in Jenkins UI.

❓ Troubleshoot

advanced

Why does Jenkins pipeline-lint command fail with 'No such file or directory'?

You run: java -jar jenkins-cli.jar -s http://jenkins.example.com/ lint-pipeline < Jenkinsfile But get error: 'No such file or directory'. What is the most likely cause?

A User lacks permission to run pipeline-lint

B Jenkins server is down

C Jenkins CLI jar is corrupted

D Jenkinsfile path is incorrect or file missing

💡 Hint

Check the file you are redirecting as input.

The error means the shell cannot find the Jenkinsfile at the given path.

🔀 Workflow

advanced

Order the steps to validate a Jenkins pipeline using CLI before running it

Arrange these steps in the correct order to validate a Jenkins pipeline using Jenkins CLI:

A 3,1,2,4

B 1,3,2,4

C 3,2,1,4

D 1,2,3,4

💡 Hint

You must have the Jenkinsfile ready before linting.

First prepare the Jenkinsfile, then lint it, fix errors if any, then run the pipeline.

✅ Best Practice

expert

What is the best practice to integrate pipeline linting in CI/CD workflow?

Which approach best integrates Jenkins pipeline linting into an automated CI/CD workflow?

A Run lint-pipeline as a Jenkins job step before pipeline execution

B Manually run lint-pipeline from Jenkins CLI before each deployment

C Run lint-pipeline command in a pre-commit Git hook locally

D Skip linting and rely on pipeline runtime errors

💡 Hint

Automation inside Jenkins is preferred for CI/CD.

Running lint-pipeline as a Jenkins job step automates validation before pipeline runs, preventing broken pipelines.