Jenkins configuration as code (JCasC) - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

JCasC YAML Loading Behavior

Given this Jenkins Configuration as Code (JCasC) YAML snippet, what will be the output when Jenkins loads it?

jenkins:
  systemMessage: "Welcome to Jenkins"
  numExecutors: 3
  securityRealm:
    local:
      allowsSignup: false
      users:
        - id: "admin"
          password: "admin123"

A Jenkins fails to load the configuration due to missing 'authorizationStrategy' section and throws an error.

B Jenkins ignores the 'numExecutors' setting and uses default 2 executors, but sets system message and user correctly.

C Jenkins sets system message to 'Welcome to Jenkins', number of executors to 3, and creates a local user 'admin' with password 'admin123'.

D Jenkins sets system message and executors but does not create any users because 'users' list is empty.

💡 Hint

Check if the YAML defines required fields for system message, executors, and local users.

The YAML snippet correctly defines systemMessage, numExecutors, and a local security realm with one user. Jenkins will apply these settings on load.

❓ Troubleshoot

intermediate

Troubleshooting JCasC Plugin Failure

You applied a JCasC YAML file to Jenkins but the configuration did not apply and Jenkins logs show:

java.lang.IllegalArgumentException: No enum constant jenkins.security.s2m.AdminWhitelistRule

What is the most likely cause?

A The YAML file contains an invalid value for the 'authorizationStrategy' field.

B The Jenkins instance is missing the JCasC plugin entirely.

C The Jenkins home directory is not writable by the Jenkins process.

D The YAML file is missing the 'jenkins' root key.

💡 Hint

Look at the error mentioning 'No enum constant' related to security.

The error indicates an invalid enum value was given in the YAML for a security setting, likely 'authorizationStrategy'.

❓ Configuration

advanced

Configuring Jenkins Global Tools with JCasC

Which YAML snippet correctly configures a JDK installation named 'jdk11' with JAVA_HOME '/usr/lib/jvm/java-11-openjdk' using Jenkins Configuration as Code?

A

tool:
  jdk:
    installations:
      - name: "jdk11"
        home: "/usr/lib/jvm/java-11-openjdk"

B

jenkins:
  tools:
    jdk:
      installations:
        - name: "jdk11"
          home: "/usr/lib/jvm/java-11-openjdk"

C

jenkins:
  tool:
    jdk:
      installations:
        - name: "jdk11"
          home: "/usr/lib/jvm/java-11-openjdk"

D

tools:
  jdk:
    installations:
      - name: "jdk11"
        home: "/usr/lib/jvm/java-11-openjdk"

💡 Hint

Global tools are configured under the 'jenkins' root key and 'tools' section.

The correct JCasC syntax places tools under 'jenkins.tools.jdk.installations'.

🔀 Workflow

advanced

JCasC and Pipeline Job Creation

You want to create a Jenkins pipeline job named 'build-app' using JCasC. Which approach is correct?

A Use JCasC to configure Jenkins system only; jobs must be created manually.

B JCasC does not support job creation; use Job DSL or REST API instead.

C Create a seed job with Job DSL and then export its configuration to JCasC YAML.

D Define the pipeline job under 'jobs:' section in JCasC YAML with its pipeline script inline.

💡 Hint

JCasC supports job definitions under a specific section.

JCasC can define jobs under the 'jobs:' key with full job configuration including pipeline scripts.

✅ Best Practice

expert

Best Practice for Managing Secrets in JCasC

What is the recommended way to manage sensitive credentials when using Jenkins Configuration as Code (JCasC)?

A Use Jenkins Credentials Plugin and reference credentials by ID in JCasC YAML without storing secrets in the YAML.

B Store all secrets directly in the JCasC YAML file encrypted with a custom key.

C Embed secrets as plain text in the JCasC YAML but restrict file system permissions tightly.

D Use environment variables in the JCasC YAML to inject secrets at runtime.

💡 Hint

Consider security best practices for secret management in Jenkins.

The best practice is to store secrets securely in Jenkins Credentials Plugin and reference them by ID in JCasC YAML, avoiding secrets in plain text files.