Pipeline validation in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code for the build stage.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh '[1]'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Ajenkins validate

Bmvn clean install

Cdocker build .

Dnpm start

Attempts:

3 left

💡 Hint

Common Mistakes

Using Jenkins CLI commands inside the shell step.

Using commands unrelated to building the project.

The sh step runs shell commands. mvn clean install is a typical command used in the build stage.

2fill in blank

medium

Complete the code to check the pipeline syntax using Jenkins CLI.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 [1] < Jenkinsfile

Drag options to blanks, or click blank then click option'

Abuild

Bvalidate-pipeline

Ccheck-syntax

Ddeclarative-linter

Attempts:

3 left

💡 Hint

Common Mistakes

Using commands like build which trigger builds instead of validation.

Guessing commands that do not exist in Jenkins CLI.

The Jenkins CLI command declarative-linter checks the syntax of a declarative pipeline.

3fill in blank

hard

Fix the error in the pipeline syntax validation command.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 [1] < Jenkinsfile

Drag options to blanks, or click blank then click option'

Arun-pipeline

Bbuild

Cdeclarative-linter

Dvalidate

Attempts:

3 left

💡 Hint

Common Mistakes

Using build which triggers a build instead of validation.

Using non-existent commands like validate.

The correct Jenkins CLI command to validate pipeline syntax is declarative-linter. Other commands either do not exist or perform different actions.

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline stage that validates the pipeline syntax before running.

Jenkins

stage('Validate') {
  steps {
    script {
      def result = sh(script: '[1]', returnStatus: true)
      if (result [2] 0) {
        error('Pipeline syntax validation failed')
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Ajava -jar jenkins-cli.jar -s http://localhost:8080 declarative-linter < Jenkinsfile

B==

C!=

Decho 'Validation passed'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '!=' to detect failure.

Using an echo command instead of the validation command.

The shell command runs the Jenkins CLI declarative-linter to check syntax. The returnStatus: true captures the exit code. If the result is not zero (!= 0), it means validation failed, so the pipeline errors out.

5fill in blank

hard

Fill all three blanks to create a Jenkins pipeline snippet that validates the pipeline syntax and aborts if invalid.

Jenkins

pipeline {
  agent any
  stages {
    stage('Validate Pipeline') {
      steps {
        script {
          def status = sh(script: '[1]', returnStatus: true)
          if (status [2] 0) {
            [3]('Pipeline syntax is invalid, aborting build')
          }
        }
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Ajava -jar jenkins-cli.jar -s http://localhost:8080 declarative-linter < Jenkinsfile

B!=

Cerror

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '!=' to detect failure.

Using 'echo' instead of 'error' to abort the build.

Incorrect Jenkins CLI command syntax.

The shell command runs the Jenkins CLI declarative-linter to validate the pipeline. If the status is not zero (!= 0), it means validation failed, so the error step aborts the build with a message.