Why multi-branch pipelines matter in Jenkins - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a multi-branch pipeline in Jenkinsfile.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        [1] 'echo Building...'
      }
    }
  }
}

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

Abat

Bscript

Csh

Dinput

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'script' instead of 'sh' for shell commands.

The sh step runs shell commands in Jenkins pipelines, which is common for build steps.

2fill in blank

medium

Complete the code to specify the branch source in a Jenkins multi-branch pipeline configuration.

Jenkins

multibranchPipelineJob('example') {
  branchSources {
    git {
      id('[1]')
      remote('https://github.com/example/repo.git')
    }
  }
}

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

A1234abcd

Bmain

Corigin

Dmaster

Attempts:

3 left

💡 Hint

Common Mistakes

Using branch names like 'main' or 'master' as the id.

The id is a unique identifier for the branch source, usually a random string or hash.

3fill in blank

hard

Fix the error in the Jenkinsfile to correctly define a multi-branch pipeline stage.

Jenkins

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        [1] 'echo Testing...'
      }
    }
  }
}

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

Abat

Bsh

Cinput

Dstage

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stage' inside steps or 'input' instead of 'sh'.

The sh step is used to run shell commands in Jenkins pipelines, which is correct here.

4fill in blank

hard

Fill both blanks to complete the Jenkins multi-branch pipeline script that checks out the code and runs a build.

Jenkins

pipeline {
  agent any
  stages {
    stage('Checkout') {
      steps {
        [1] scm
      }
    }
    stage('Build') {
      steps {
        [2] 'make build'
      }
    }
  }
}

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

Acheckout

Bsh

Cbat

Dscript

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'script' instead of 'sh' for build commands.

checkout scm checks out the source code. sh runs the build command in shell.

5fill in blank

hard

Fill all three blanks to create a Jenkins multi-branch pipeline that triggers on branch changes, checks out code, and runs tests.

Jenkins

multibranchPipelineJob('project') {
  triggers {
    [1] {
      interval('1d')
    }
  }
  branchSources {
    git {
      id('abc123')
      remote('https://github.com/example/project.git')
    }
  }
  factory {
    workflowBranchProjectFactory {
      scriptPath('[2]')
    }
  }
}
pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        [3] 'pytest'
      }
    }
  }
}

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

AperiodicFolderTrigger

BJenkinsfile

Csh

DpollSCM

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pollSCM' instead of 'periodicFolderTrigger' for triggers.

periodicFolderTrigger triggers the job periodically. Jenkinsfile is the default pipeline script file. sh runs shell commands like tests.