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.

Practice

1. What is the main purpose of Jenkins Configuration as Code (JCasC)?

easy

A. To monitor Jenkins server performance

B. To write Jenkins plugins in Java

C. To define Jenkins setup using a YAML file for easy automation

D. To create Jenkins jobs manually through the UI

Solution

1. Step 1: Understand JCasC concept

   JCasC allows Jenkins setup to be described in a YAML file instead of manual UI steps.

2. Step 2: Identify the main benefit

   This YAML file makes automation, sharing, and repeating Jenkins setup easy and safe.

3. Final Answer:

   To define Jenkins setup using a YAML file for easy automation -> Option C

4. Quick Check:

   JCasC = YAML setup automation [OK]

Hint: JCasC means Jenkins setup in YAML file [OK]

Common Mistakes:

• Confusing JCasC with plugin development
• Thinking JCasC is for manual UI job creation
• Assuming JCasC monitors performance

2. Which of the following is the correct syntax to define Jenkins system message in a JCasC YAML file?

easy

A. jenkins:
systemMessage: "Welcome to Jenkins!"

B. jenkins:
system_message: "Welcome to Jenkins!"

C. jenkins:
system-message: "Welcome to Jenkins!"

D. jenkins:
system message: "Welcome to Jenkins!"

Solution

1. Step 1: Check YAML key naming conventions

   JCasC uses camelCase keys matching Jenkins config names, so 'systemMessage' is correct.

2. Step 2: Validate YAML syntax

   jenkins: systemMessage: "Welcome to Jenkins!" uses correct key and proper YAML indentation and quotes.

3. Final Answer:

   jenkins:\n systemMessage: "Welcome to Jenkins!" -> Option A

4. Quick Check:

   Correct key is systemMessage in YAML [OK]

Hint: Use camelCase keys exactly as Jenkins expects [OK]

Common Mistakes:

• Using underscores instead of camelCase
• Using spaces or dashes in keys
• Incorrect YAML indentation

3. Given this JCasC snippet, what will be the Jenkins admin username after applying it?

jenkins:
  securityRealm:
    local:
      allowsSignup: false
      users:
        - id: "admin"
          password: "admin123"

medium

A. root

B. user

C. guest

D. admin

Solution

1. Step 1: Read the users list in securityRealm

   The YAML defines one user with id 'admin' and password 'admin123'.

2. Step 2: Identify the admin username

   The user id 'admin' is the admin username set by this config.

3. Final Answer:

   admin -> Option D

4. Quick Check:

   User id in YAML = admin [OK]

Hint: Look for 'id' under users in securityRealm [OK]

Common Mistakes:

• Assuming default username instead of YAML value
• Confusing password with username
• Ignoring YAML indentation and structure

4. You applied this JCasC YAML but Jenkins failed to start:

jenkins:
  systemMessage "Hello Jenkins!"

What is the error in this configuration?

medium

A. Incorrect indentation of systemMessage

B. Missing colon ':' after systemMessage key

C. systemMessage should be under securityRealm

D. Quotes around Hello Jenkins! are not allowed

Solution

1. Step 1: Check YAML key-value syntax

   YAML requires a colon ':' after keys to separate them from values.

2. Step 2: Identify missing colon

   The line 'systemMessage "Hello Jenkins!"' misses the colon after systemMessage.

3. Final Answer:

   Missing colon ':' after systemMessage key -> Option B

4. Quick Check:

   YAML key:value needs colon [OK]

Hint: YAML keys must have colon ':' before values [OK]

Common Mistakes:

• Forgetting colon after key
• Misplacing keys under wrong parent
• Thinking quotes are forbidden

5. You want to automate Jenkins setup with JCasC to create two users: 'alice' and 'bob'. Which YAML snippet correctly defines both users with passwords?

hard

A. jenkins:
securityRealm:
local:
allowsSignup: false
users:
- id: "alice"
password: "alicePass"
- id: "bob"
password: "bobPass"

B. jenkins:
securityRealm:
local:
allowsSignup: false
users:
id: "alice"
password: "alicePass"
id: "bob"
password: "bobPass"

C. jenkins:
securityRealm:
local:
allowsSignup: false
users:
alice: "alicePass"
bob: "bobPass"

D. jenkins:
securityRealm:
local:
allowsSignup: false
users:
- alice: "alicePass"
- bob: "bobPass"

Solution

1. Step 1: Understand users list format

   Users must be a list of maps with 'id' and 'password' keys for each user.

2. Step 2: Check each option's structure

   jenkins: securityRealm: local: allowsSignup: false users: - id: "alice" password: "alicePass" - id: "bob" password: "bobPass" correctly uses a list with '- id' and 'password' pairs for alice and bob.

3. Final Answer:

   jenkins:\n securityRealm:\n local:\n allowsSignup: false\n users:\n - id: "alice"\n password: "alicePass"\n - id: "bob"\n password: "bobPass" -> Option A

4. Quick Check:

   Users list with id/password pairs = jenkins: securityRealm: local: allowsSignup: false users: - id: "alice" password: "alicePass" - id: "bob" password: "bobPass" [OK]

Hint: Users must be list items with id and password keys [OK]

Common Mistakes:

• Defining users as a map instead of list
• Repeating keys without list dash
• Using username as key instead of id