Organization folders in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Organization Folder in Jenkins using the Jenkins CLI.

Jenkins

java -jar jenkins-cli.jar -s http://jenkins.example.com create-job [1] < orgfolder-config.xml

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

AMyOrgFolder

BNewJob

CPipelineJob

DSimpleFolder

Attempts:

3 left

💡 Hint

Common Mistakes

Using a job name instead of an organization folder name.

The name MyOrgFolder is used to create an Organization Folder. Other names refer to different job types.

2fill in blank

medium

Complete the code to list all Organization Folders in Jenkins using the REST API.

Jenkins

curl -s http://jenkins.example.com/api/json?tree=jobs[name,[1]] | jq '.'

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

Acolor

Bclass

Cdescription

Durl

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'url' or 'color' which do not identify job types.

The class field helps identify Organization Folders by their job type in the JSON output.

3fill in blank

hard

Fix the error in the Jenkins pipeline script to create an Organization Folder using the Jenkins Job DSL plugin.

Jenkins

organizationFolder('[1]') {
  displayName('My Organization')
}

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

Asimple-folder

Bpipeline-job

Cmy-org-folder

Dfreestyle-job

Attempts:

3 left

💡 Hint

Common Mistakes

Using job names instead of folder names.

The folder name my-org-folder is valid for an Organization Folder. Other options refer to different job types.

4fill in blank

hard

Fill both blanks to configure an Organization Folder with a source and a strategy in Jenkins Job DSL.

Jenkins

organizationFolder('MyOrg') {
  [1] {
    id('github')
  }
  [2] {
    strategy('AllBranches')
  }
}

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

Asources

Btriggers

Cscm

DfolderProperties

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'triggers' or 'scm' incorrectly in this context.

sources defines the source repositories, and folderProperties can define strategies or properties for the folder.

5fill in blank

hard

Fill all three blanks to define an Organization Folder with a GitHub source, a branch discovery strategy, and a trigger in Jenkins Job DSL.

Jenkins

organizationFolder('MyOrg') {
  sources {
    [1] {
      id('github')
      repoOwner('my-org')
      repository('my-repo')
    }
  }
  [2] {
    strategy('DiscoverBranches')
  }
  [3] {
    cron('H/15 * * * *')
  }
}

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

Agithub

BfolderProperties

Ctriggers

Dscm

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 'scm' and 'github' or placing triggers incorrectly.

github defines the GitHub source, folderProperties sets the branch strategy, and triggers configures periodic scanning.

Practice

1. What is the main purpose of an Organization Folder in Jenkins?

easy

A. To automatically group and manage multiple projects from source control

B. To manually create individual jobs one by one

C. To store Jenkins system configuration files

D. To run Jenkins on multiple servers

Solution

1. Step 1: Understand the role of Organization Folders

   Organization Folders scan source control and group many projects automatically.

2. Step 2: Compare options with this role

   Only To automatically group and manage multiple projects from source control describes automatic grouping and management from source control.

3. Final Answer:

   To automatically group and manage multiple projects from source control -> Option A

4. Quick Check:

   Organization Folder = automatic project grouping [OK]

Hint: Organization folders auto-group projects from repos [OK]

Common Mistakes:

• Thinking organization folders create jobs manually
• Confusing folders with Jenkins system files
• Assuming folders run Jenkins on servers

2. Which of the following is the correct way to create an Organization Folder in Jenkins UI?

easy

A. Manage Jenkins > Configure System > Add Organization Folder

B. New Item > Enter name > Select 'Organization Folder' > OK

C. Dashboard > New Job > Select 'Freestyle Project'

D. Manage Plugins > Install Organization Folder Plugin

Solution

1. Step 1: Recall how to create new items in Jenkins

   New items are created via 'New Item' on the dashboard.

2. Step 2: Identify the correct selection for Organization Folder

   Choosing 'Organization Folder' after naming is the correct step.

3. Final Answer:

   New Item > Enter name > Select 'Organization Folder' > OK -> Option B

4. Quick Check:

   Create folder via New Item > Organization Folder [OK]

Hint: Create folder via New Item, then choose Organization Folder [OK]

Common Mistakes:

• Trying to add folder in Configure System
• Selecting Freestyle Project instead of Organization Folder
• Confusing plugin installation with folder creation

3. Given an Organization Folder configured to scan a GitHub organization, what will Jenkins do when it scans the source control?

medium

A. Delete all existing jobs and create a single job for the organization

B. Fail to scan unless manually triggered each time

C. Only scan the first repository and ignore others

D. Create individual jobs for each repository found in the organization

Solution

1. Step 1: Understand scanning behavior of Organization Folders

   They scan all repositories in the source control organization and create jobs for each.

2. Step 2: Evaluate options against this behavior

   Create individual jobs for each repository found in the organization matches this automatic job creation per repo.

3. Final Answer:

   Create individual jobs for each repository found in the organization -> Option D

4. Quick Check:

   Scan creates jobs per repo automatically [OK]

Hint: Scan creates jobs for all repos found [OK]

Common Mistakes:

• Thinking it deletes all jobs
• Assuming only first repo is scanned
• Believing manual trigger is always needed

4. You created an Organization Folder but Jenkins does not show any jobs inside it after scanning. What is the most likely cause?

medium

A. Jenkins does not support Organization Folders

B. The Organization Folder plugin is not installed

C. The source control credentials are missing or incorrect

D. The Jenkins server is offline

Solution

1. Step 1: Check common reasons for empty scan results

   Missing or wrong credentials prevent Jenkins from accessing repos.

2. Step 2: Rule out other options

   Plugin must be installed to create folder; if folder exists, plugin is installed. Jenkins supports folders. Server offline would prevent all jobs, not just empty folder.

3. Final Answer:

   The source control credentials are missing or incorrect -> Option C

4. Quick Check:

   Missing credentials cause empty scan [OK]

Hint: Check credentials if folder scan shows no jobs [OK]

Common Mistakes:

• Assuming plugin is missing after folder creation
• Thinking Jenkins lacks folder support
• Blaming server offline without checking credentials

5. You want to configure an Organization Folder to scan a GitHub Enterprise server with multiple teams. Which two settings must you configure to ensure Jenkins discovers all repositories correctly?

hard

A. Set the GitHub Enterprise API endpoint and provide valid credentials

B. Enable Jenkins master node to run all jobs manually

C. Install the GitHub plugin and disable scanning

D. Configure the folder to scan only one team at a time

Solution

1. Step 1: Identify key settings for GitHub Enterprise scanning

   Jenkins needs the correct API endpoint URL and valid credentials to access the Enterprise server.

2. Step 2: Evaluate other options

   Running jobs manually or disabling scanning prevents auto-discovery. Scanning one team at a time limits coverage.

3. Final Answer:

   Set the GitHub Enterprise API endpoint and provide valid credentials -> Option A

4. Quick Check:

   API endpoint + credentials = full repo discovery [OK]

Hint: Set API endpoint and credentials for Enterprise scan [OK]

Common Mistakes:

• Disabling scanning disables discovery
• Assuming manual job runs help discovery
• Limiting scan to one team misses repos