Jenkins configuration as code (JCasC) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Jenkins system message in JCasC YAML.

Jenkins

jenkins:
  systemMessage: "[1]"

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

AWelcome to Jenkins configured by code!

BSystem is offline

CError loading config

DNo message set

Attempts:

3 left

💡 Hint

Common Mistakes

Using error or offline messages instead of a welcome message.

The systemMessage field sets the message shown on Jenkins dashboard. The correct message is the welcoming one.

2fill in blank

medium

Complete the code to enable the Jenkins security realm as 'local'.

Jenkins

jenkins:
  securityRealm:
    [1]: {}

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

Aldap

Bnone

Clocal

Dgithub

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing external authentication like ldap or github when local is needed.

The local security realm means Jenkins manages users internally.

3fill in blank

hard

Fix the error in the JCasC snippet to correctly configure the number of executors.

Jenkins

jenkins:
  numExecutors: [1]

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

A2

B-1

C"two"

Dzero

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings instead of numbers or negative values.

The numExecutors must be a positive integer. The number 2 is correct.

4fill in blank

hard

Fill both blanks to configure the Jenkins agent protocol and its enabled status.

Jenkins

jenkins:
  agentProtocols:
    - [1]
  disableRememberMe: [2]

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

AJNLP4-connect

Btrue

Cfalse

DSSH

Attempts:

3 left

💡 Hint

Common Mistakes

Using SSH as protocol when JNLP4-connect is expected.

Setting disableRememberMe to true disables remembering login.

The JNLP4-connect is a common agent protocol. The disableRememberMe should be false to allow remembering login.

5fill in blank

hard

Fill all three blanks to configure a Jenkins job with a name, description, and a simple shell build step.

Jenkins

jobs:
  - script:
      name: "[1]"
      description: "[2]"
      builders:
        - shell: "[3]"

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

AExampleJob

BThis job runs a simple shell command

Cecho Hello Jenkins

Decho Goodbye

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up job name and description.

Using unrelated shell commands.

The job name is ExampleJob, description explains the job, and the shell step prints a greeting.