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.

Practice

1. What is the main purpose of pipeline linting in Jenkins?

easy

A. To create new Jenkins jobs automatically

B. To deploy the pipeline to production

C. To check Jenkinsfile syntax before running the pipeline

D. To monitor pipeline execution time

Solution

1. Step 1: Understand pipeline linting

   Pipeline linting checks the Jenkinsfile for syntax errors before execution.

2. Step 2: Identify the main goal

   This helps catch mistakes early, avoiding broken builds.

3. Final Answer:

   To check Jenkinsfile syntax before running the pipeline -> Option C

4. Quick Check:

   Pipeline linting = syntax check [OK]

Hint: Linting means syntax check before running [OK]

Common Mistakes:

• Confusing linting with deployment
• Thinking linting monitors runtime
• Assuming linting creates jobs

2. Which Jenkins CLI command is used to lint a Jenkinsfile?

easy

A. jenkins-cli lint-jenkinsfile

B. jenkins-cli pipeline-lint

C. jenkins-cli validate-pipeline

D. jenkins-cli pipeline-validate

Solution

1. Step 1: Recall Jenkins CLI lint command

   The correct command to lint Jenkinsfiles is pipeline-validate.

2. Step 2: Match exact command

   Among options, only jenkins-cli pipeline-validate is valid syntax.

3. Final Answer:

   jenkins-cli pipeline-validate -> Option D

4. Quick Check:

   CLI lint command = pipeline-validate [OK]

Hint: Use 'pipeline-validate' with Jenkins CLI to validate [OK]

Common Mistakes:

• Using incorrect command names
• Mixing validate and lint terms
• Adding extra words in command

3. What will be the output of this command if the Jenkinsfile has a syntax error?

jenkins-cli pipeline-validate Jenkinsfile

medium

A. Validation successful: No syntax errors found

B. Error: Syntax error found in Jenkinsfile

C. Pipeline executed successfully

D. No output is shown

Solution

1. Step 1: Understand pipeline-validate output

   If the Jenkinsfile has syntax errors, the validate command reports them as errors.

2. Step 2: Identify correct output message

   The command will output an error message indicating syntax problems.

3. Final Answer:

   Error: Syntax error found in Jenkinsfile -> Option B

4. Quick Check:

   Syntax error in Jenkinsfile = error output [OK]

Hint: Syntax errors cause error messages on lint command [OK]

Common Mistakes:

• Expecting success message despite errors
• Confusing lint with pipeline run output
• Assuming no output means error

4. You run jenkins-cli pipeline-validate Jenkinsfile but get a connection refused error. What is the likely cause?

medium

A. Jenkins server is not running or unreachable

B. Jenkinsfile has syntax errors

C. The pipeline-validate command is misspelled

D. The Jenkinsfile path is incorrect

Solution

1. Step 1: Analyze connection refused error

   This error means the CLI cannot connect to the Jenkins server.

2. Step 2: Rule out other causes

   Syntax errors or file path issues cause different errors, not connection refused.

3. Final Answer:

   Jenkins server is not running or unreachable -> Option A

4. Quick Check:

   Connection refused = server down/unreachable [OK]

Hint: Connection refused means Jenkins server unreachable [OK]

Common Mistakes:

• Blaming syntax errors for connection issues
• Assuming command typo causes connection refused
• Ignoring network/server status

5. You want to automate Jenkinsfile validation in a CI job before merging code. Which approach is best?

hard

A. Run jenkins-cli pipeline-validate command in the CI job script

B. Manually check Jenkinsfile syntax after merging

C. Run the pipeline and fix errors if it fails

D. Skip validation to save time

Solution

1. Step 1: Understand automation goal

   Automating validation before merging prevents broken pipelines early.

2. Step 2: Choose best method

   Running jenkins-cli pipeline-validate in CI script checks syntax automatically.

3. Final Answer:

   Run jenkins-cli pipeline-validate command in the CI job script -> Option A

4. Quick Check:

   Automate linting in CI = run pipeline-validate [OK]

Hint: Automate linting with CLI in CI jobs [OK]

Common Mistakes:

• Waiting to fix errors after merge
• Skipping validation to save time
• Relying on manual checks