Git repository configuration in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to clone a Git repository using Jenkins pipeline.

Jenkins

git url: '[1]'

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

Assh://repo.git

Bgit clone https://github.com/example/repo.git

Crepo.git

Dhttps://github.com/example/repo.git

Attempts:

3 left

💡 Hint

Common Mistakes

Including the 'git clone' command inside the URL parameter

Using only the repository name without full URL

Using SSH URL without proper credentials

The git step in Jenkins pipeline requires the repository URL as the url parameter to clone the repository.

2fill in blank

medium

Complete the code to specify the branch to checkout in Jenkins Git step.

Jenkins

git url: 'https://github.com/example/repo.git', branch: '[1]'

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

Amain

Bfeature

Cdevelop

Dmaster

Attempts:

3 left

💡 Hint

Common Mistakes

Using branch names that do not exist in the repository

Leaving the branch parameter empty

Using 'master' when the repo uses 'main'

The branch parameter specifies which branch Jenkins should checkout. 'main' is the default branch name in many repositories.

3fill in blank

hard

Fix the error in the Jenkins pipeline Git checkout step by completing the missing parameter.

Jenkins

checkout([$class: 'GitSCM', branches: [[name: '[1]']], userRemoteConfigs: [[url: 'https://github.com/example/repo.git']]])

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

Arefs/heads/main

Bmain

Crefs/tags/v1.0

DHEAD

Attempts:

3 left

💡 Hint

Common Mistakes

Using just 'main' instead of 'refs/heads/main'

Using tag refs when a branch is expected

Using 'HEAD' which is ambiguous

When using checkout with GitSCM, the branch name must be specified as a full ref, like refs/heads/main.

4fill in blank

hard

Fill both blanks to configure Git credentials and repository URL in Jenkins pipeline.

Jenkins

git url: '[1]', credentialsId: '[2]'

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

Ahttps://github.com/example/repo.git

Bgit-credentials-id-123

Cssh://github.com/example/repo.git

Duser-credentials-id

Attempts:

3 left

💡 Hint

Common Mistakes

Using SSH URL without matching credentials

Using wrong credentials ID

Mixing URL and credentials values

The url parameter specifies the Git repository URL, and credentialsId specifies the Jenkins stored credentials to access the repo.

5fill in blank

hard

Fill all three blanks to create a Jenkins pipeline step that checks out a specific branch with credentials.

Jenkins

checkout([$class: 'GitSCM', branches: [[name: '[1]']], userRemoteConfigs: [[url: '[2]', credentialsId: '[3]']]])

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

Arefs/heads/develop

Bhttps://github.com/example/repo.git

Cgit-credentials-id-456

Drefs/tags/v2.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using tag refs instead of branch refs

Incorrect or missing credentials ID

Using incomplete branch names

This checkout step specifies the branch as a full ref, the repository URL, and the credentials ID to authenticate.

Practice

1. What is the main purpose of configuring a Git repository in Jenkins?

easy

A. To set the Jenkins server's IP address

B. To tell Jenkins where to find the source code for building

C. To configure Jenkins user permissions

D. To install Jenkins plugins automatically

Solution

1. Step 1: Understand Jenkins and Git integration

   Jenkins needs to know the location of the source code to build and test it automatically.

2. Step 2: Identify the role of Git repository configuration

   Configuring the Git repository provides Jenkins with the URL and branch to fetch the code.

3. Final Answer:

   To tell Jenkins where to find the source code for building -> Option B

4. Quick Check:

   Git repo config = source code location [OK]

Hint: Git repo config tells Jenkins where code lives [OK]

Common Mistakes:

• Confusing repository URL with Jenkins server settings
• Thinking Git config sets user permissions
• Assuming it installs plugins automatically

2. Which of the following is the correct way to specify a Git repository URL in Jenkins?

easy

A. C:\Users\repo

B. http://jenkins.local/repo.git

C. [e-mail]:user/repo.git

D. ftp://github.com/user/repo.git

Solution

1. Step 1: Identify valid Git repository URL formats

   Git URLs typically use SSH (git@...) or HTTPS (https://...) protocols.

2. Step 2: Check each option's format

   [e-mail]:user/repo.git uses SSH format, which is valid. http://jenkins.local/repo.git is a Jenkins URL, not a Git repo. C:\Users\repo is a Windows path, not a URL. ftp://github.com/user/repo.git uses FTP, which Git does not use.

3. Final Answer:

   [e-mail]:user/repo.git -> Option C

4. Quick Check:

   SSH or HTTPS URL = valid Git repo URL [OK]

Hint: Git URLs use SSH or HTTPS, not local paths or FTP [OK]

Common Mistakes:

• Using local file paths instead of URLs
• Confusing Jenkins URLs with Git URLs
• Using unsupported protocols like FTP

3. Given this Jenkins Git configuration snippet:

Repository URL: https://github.com/example/project.git
Branch Specifier: feature-branch

What will Jenkins do when it runs a build?

medium

A. Clone the 'feature-branch' branch from the repository

B. Fail because branch specifier is missing

C. Clone all branches from the repository

D. Clone the 'main' branch from the repository

Solution

1. Step 1: Understand the Branch Specifier field

   The Branch Specifier tells Jenkins which branch to clone and build.

2. Step 2: Analyze the given branch specifier

   The branch is set to 'feature-branch', so Jenkins will clone that specific branch.

3. Final Answer:

   Clone the 'feature-branch' branch from the repository -> Option A

4. Quick Check:

   Branch Specifier = selected branch [OK]

Hint: Branch Specifier sets which branch Jenkins clones [OK]

Common Mistakes:

• Assuming Jenkins always clones 'main' branch
• Thinking Jenkins clones all branches by default
• Believing branch specifier can be empty

4. You configured Jenkins with this Git repository URL:
https://github.com/example/project.git
But the build fails with authentication errors. What is the most likely cause?

medium

A. Credentials are missing or incorrect in Jenkins Git config

B. The branch name is misspelled

C. The repository URL is incorrect

D. Jenkins server is offline

Solution

1. Step 1: Understand authentication in Git with Jenkins

   Private repositories require credentials for Jenkins to access them.

2. Step 2: Analyze the error cause

   Authentication errors usually mean Jenkins lacks correct credentials or they are not configured.

3. Final Answer:

   Credentials are missing or incorrect in Jenkins Git config -> Option A

4. Quick Check:

   Authentication error = check credentials [OK]

Hint: Authentication errors mean missing or wrong credentials [OK]

Common Mistakes:

• Assuming URL is always wrong for auth errors
• Ignoring credentials setup in Jenkins
• Blaming branch name for authentication issues

5. You want Jenkins to build code from a private Git repository using SSH keys. Which steps must you take to configure this correctly?

hard

A. Upload the repository code manually to Jenkins workspace

B. Use HTTPS URL and enter username/password in Jenkins Git config

C. Set the repository URL to HTTP and disable authentication

D. Add the SSH private key in Jenkins credentials and use the SSH Git URL

Solution

1. Step 1: Use SSH URL for private repo access

   SSH URLs look like [e-mail]:user/repo.git and allow key-based authentication.

2. Step 2: Add SSH private key to Jenkins credentials

   Jenkins needs the private key stored securely to authenticate with the Git server.

3. Step 3: Configure Jenkins Git plugin to use SSH URL and credentials

   Set the repository URL to the SSH format and select the SSH key credential in Jenkins.

4. Final Answer:

   Add the SSH private key in Jenkins credentials and use the SSH Git URL -> Option D

5. Quick Check:

   SSH key + SSH URL = secure private repo access [OK]

Hint: Use SSH URL + private key credential for private repos [OK]

Common Mistakes:

• Using HTTP URL without credentials for private repos
• Trying to disable authentication for private repos
• Uploading code manually instead of using Git