Job configuration sections in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the section for build steps in a Jenkins job configuration.

Jenkins

<builders>[1]</builders>

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

A<actions>

B<buildSteps>

C<steps>

D<build>

Attempts:

3 left

💡 Hint

Common Mistakes

Using which is not a valid Jenkins XML tag.

Using which is unrelated to build steps.

The section contains the element which defines the build steps in Jenkins job configuration.

2fill in blank

medium

Complete the code to specify the triggers section in a Jenkins job configuration.

Jenkins

<triggers>[1]</triggers>

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

A<schedule>

B<hudson.triggers.TimerTrigger>

C<pollSCM>

D<cron>

Attempts:

3 left

💡 Hint

Common Mistakes

Using which is a schedule format but not the XML tag.

Using which is a different trigger type.

The tag defines a timer trigger in Jenkins job configuration inside the section.

3fill in blank

hard

Fix the error in the post-build actions section by completing the missing tag.

Jenkins

<publishers>[1]</publishers>

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

A<hudson.tasks.ArtifactArchiver>

B<actions>

C<postBuildActions>

D<postActions>

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic tags like which are not specific post-build action tags.

Using which is not a valid Jenkins XML tag.

The tag is used inside to define post-build actions like archiving artifacts.

4fill in blank

hard

Fill both blanks to complete the environment variables section in Jenkins job configuration.

Jenkins

<properties>[1][2]</properties>

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

A<EnvInjectJobProperty>

B<ParametersDefinitionProperty>

C<info>

D<environment>

Attempts:

3 left

💡 Hint

Common Mistakes

Using which is for build parameters, not environment variables.

Using which is not related to environment variables.

The tag is used inside to inject environment variables, and defines the variables themselves.

5fill in blank

hard

Fill all three blanks to complete the Jenkins job configuration snippet for SCM, triggers, and builders sections.

Jenkins

<scm class="[1]">[2]</scm>
<triggers>[3]</triggers>
<builders>
  <hudson.tasks.Shell>
    <command>echo Hello</command>
  </hudson.tasks.Shell>
</builders>

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

Ahudson.plugins.git.GitSCM

B<branches><hudson.plugins.git.BranchSpec><name>*/main</name></hudson.plugins.git.BranchSpec></branches>

C<hudson.triggers.TimerTrigger><spec>H/15 * * * *</spec></hudson.triggers.TimerTrigger>

D<hudson.tasks.BatchFile>

Attempts:

3 left

💡 Hint

Common Mistakes

Using inside SCM or triggers sections.

Incorrect branch specification tags.

The SCM class for Git is . The branches are defined inside . The trigger uses with a schedule.

Practice

1. Which section in a Jenkins job configuration is used to divide the process into steps like build, test, and deploy?

easy

A. Triggers

B. Post

C. Environment

D. Stages

Solution

1. Step 1: Understand Jenkins job structure

   Jenkins jobs are organized into sections to manage tasks clearly.

2. Step 2: Identify the section for dividing tasks

   The 'Stages' section splits the job into steps like build, test, and deploy.

3. Final Answer:

   Stages -> Option D

4. Quick Check:

   Stages = Steps division [OK]

Hint: Stages split tasks into steps like build and test [OK]

Common Mistakes:

• Confusing Post section with Stages
• Thinking Environment defines steps
• Mixing Triggers with task division

2. Which of the following is the correct syntax to define a post section in a Jenkins declarative pipeline?

easy

A. post { always { echo 'Done' } }

B. post: { always: { echo 'Done' } }

C. post => { always => { echo 'Done' } }

D. post = { always = { echo 'Done' } }

Solution

1. Step 1: Recall Jenkins declarative syntax

   Jenkins uses braces and keywords without colons or arrows in declarative pipelines.

2. Step 2: Check each option's syntax

   post { always { echo 'Done' } } uses correct braces and keywords: post { always { ... } }.

3. Final Answer:

   post { always { echo 'Done' } } -> Option A

4. Quick Check:

   Correct post syntax uses braces and keywords [OK]

Hint: Use braces and keywords without colons or arrows [OK]

Common Mistakes:

• Using colons instead of braces
• Using arrows => instead of braces
• Assigning with = instead of braces

3. Given this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
  post {
    success {
      echo 'Build succeeded'
    }
    failure {
      echo 'Build failed'
    }
  }
}

What will Jenkins print if the build step runs without errors?

medium

A. Build succeeded

B. Building...
Build succeeded

C. Building...
Build failed

D. Build failed

Solution

1. Step 1: Analyze the stages and steps

   The 'Build' stage prints 'Building...'. If no errors occur, it succeeds.

2. Step 2: Check post section behavior

   On success, it prints 'Build succeeded'. On failure, 'Build failed'.

3. Final Answer:

   Building... Build succeeded -> Option B

4. Quick Check:

   Success triggers 'Build succeeded' after build step [OK]

Hint: Success post runs only if build passes [OK]

Common Mistakes:

• Assuming failure message prints on success
• Ignoring the initial build echo
• Confusing post section triggers

4. You wrote this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        echo 'Testing...'
      }
    }
  }
  post {
    always echo 'Cleaning up'
  }
}

But Jenkins throws a syntax error. What is the likely cause?

medium

A. Missing braces around the 'always' block

B. Incorrect indentation inside 'stages'

C. Using 'always' inside 'post' without a condition

D. Missing 'steps' block inside 'always'

Solution

1. Step 1: Review 'post' section syntax

   Each condition like 'always' must be followed by braces { ... } containing steps or actions.

2. Step 2: Check the given snippet

   'always echo ...' lacks braces after 'always', causing a syntax error.

3. Final Answer:

   Missing braces around the 'always' block -> Option A

4. Quick Check:

   Post conditions need braces { block } [OK]

Hint: Post conditions like 'always' require { block } [OK]

Common Mistakes:

• Forgetting braces around post condition blocks
• Assuming indentation causes syntax error
• Thinking 'always' needs no condition

5. You want a Jenkins job to run these steps: build, test, and deploy. You also want to send a notification only if the deploy step fails. Which job configuration sections should you use to organize this?

hard

A. Use 'post' for build, test, deploy; use 'stages' with 'failure' for notification

B. Use 'environment' for build, test, deploy; use 'post' with 'always' for notification

C. Use 'stages' for build, test, deploy; use 'post' with 'failure' for notification

D. Use 'triggers' for build, test, deploy; use 'post' with 'success' for notification

Solution

1. Step 1: Organize main tasks

   Use 'stages' section to split the job into build, test, and deploy steps.

2. Step 2: Handle failure notifications

   Use 'post' section with 'failure' condition to send notification if deploy fails.

3. Final Answer:

   Use 'stages' for build, test, deploy; use 'post' with 'failure' for notification -> Option C

4. Quick Check:

   Stages for tasks, post failure for alerts [OK]

Hint: Stages for steps, post failure for alerts [OK]

Common Mistakes:

• Putting main tasks inside post section
• Using post success instead of failure for alerts
• Confusing triggers with task steps