Credentials for Git access in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Jenkins Git Credentials Types

Which type of Jenkins credential is best suited for accessing a private Git repository using SSH keys?

A SSH Username with private key

B Certificate

C Secret text

D Username and password

💡 Hint

Think about what is commonly used for secure Git access over SSH.

SSH Username with private key is the recommended credential type for Git access over SSH in Jenkins. It uses a private key for authentication without exposing passwords.

💻 Command Output

intermediate

Jenkins Git Credential Usage Output

What will be the output of the Jenkins pipeline step when using a Git credential with ID 'git-creds' to clone a private repository?

pipeline {
  agent any
  stages {
    stage('Clone') {
      steps {
        git url: '[e-mail]:example/private-repo.git', credentialsId: 'git-creds'
      }
    }
  }
}

A Clones the repository successfully without asking for username or password

B Fails with authentication error due to missing credentials

C Prompts for username and password interactively

D Clones the repository but ignores the credentialsId

💡 Hint

Jenkins uses the credentialsId to authenticate automatically.

When the correct credentialsId is provided, Jenkins uses it to authenticate and clone the private Git repository without manual input.

❓ Configuration

advanced

Configuring Jenkins Credentials for Git HTTPS Access

Which Jenkins credential configuration is correct for accessing a private Git repository over HTTPS that requires a username and personal access token?

A SSH Username with private key

B Username with password, where password is the personal access token

C Secret file containing the token

D Certificate with private key

💡 Hint

HTTPS Git access usually requires username and token as password.

For HTTPS Git access, Jenkins credentials should be set as 'Username with password', where the password is the personal access token from the Git provider.

❓ Troubleshoot

advanced

Troubleshooting Jenkins Git Credential Errors

Jenkins fails to clone a private Git repository with the error: 'Authentication failed'. The pipeline uses a credentialsId for SSH access. What is the most likely cause?

A The Jenkins agent does not have Git installed

B The repository URL is using HTTPS instead of SSH

C The credentialsId is not specified in the pipeline

D The private key in Jenkins credentials is missing or invalid

💡 Hint

Check the private key validity in Jenkins credentials.

If the private key is missing or invalid, SSH authentication will fail causing the error.

🔀 Workflow

expert

Securely Managing Git Credentials in Jenkins Pipeline

Which Jenkins pipeline snippet securely uses Git credentials stored in Jenkins to clone a private repository and avoids exposing credentials in logs?

A withCredentials([usernamePassword(credentialsId: 'git-creds', usernameVariable: 'USER', passwordVariable: 'PASS')]) { sh 'git clone https://$USER:$[e-mail]/example/private-repo.git' }

B sh 'git clone https://username:[e-mail]/example/private-repo.git'

C git url: '[e-mail]:example/private-repo.git', credentialsId: 'git-creds'

D sh 'git clone [e-mail]:example/private-repo.git'

💡 Hint

Consider Jenkins built-in Git step and credential masking.

Using the Jenkins 'git' step with credentialsId automatically masks credentials and avoids exposing them in logs, unlike manual shell commands.

Practice

1. What is the main purpose of adding credentials in Jenkins for Git access?

easy

A. To create new Git repositories automatically

B. To speed up the Jenkins build process

C. To enable Jenkins to run on multiple nodes

D. To allow Jenkins to securely access private Git repositories

Solution

1. Step 1: Understand Jenkins and Git integration

   Jenkins needs credentials to authenticate and access private Git repositories securely.

2. Step 2: Identify the purpose of credentials

   Credentials store authentication details like username/password or SSH keys for Git access.

3. Final Answer:

   To allow Jenkins to securely access private Git repositories -> Option D

4. Quick Check:

   Credentials = Secure Git access [OK]

Hint: Credentials = secure login for Jenkins to Git [OK]

Common Mistakes:

• Thinking credentials speed up builds
• Confusing credentials with Jenkins nodes
• Assuming credentials create repos

2. Which Jenkins menu path do you use to add Git credentials?

easy

A. Manage Jenkins > Configure System

B. Manage Jenkins > Manage Credentials

C. New Item > Pipeline

D. Build History > Credentials

Solution

1. Step 1: Locate where Jenkins stores credentials

   Jenkins stores credentials under 'Manage Credentials' accessible from 'Manage Jenkins'.

2. Step 2: Confirm the correct menu path

   The correct path to add or manage Git credentials is 'Manage Jenkins > Manage Credentials'.

3. Final Answer:

   Manage Jenkins > Manage Credentials -> Option B

4. Quick Check:

   Manage Credentials = Add Git credentials [OK]

Hint: Add credentials under Manage Jenkins > Manage Credentials [OK]

Common Mistakes:

• Choosing Configure System instead of Manage Credentials
• Selecting New Item which creates jobs
• Looking in Build History which shows past builds

3. Given this Jenkins pipeline snippet, what does credentials('git-cred-id') represent?

pipeline {
  agent any
  stages {
    stage('Checkout') {
      steps {
        git url: 'https://github.com/example/repo.git', credentialsId: 'git-cred-id'
      }
    }
  }
}

medium

A. The Jenkins credential ID used for Git authentication

B. The Jenkins agent label

C. The branch name to checkout

D. The ID of the Git repository

Solution

1. Step 1: Understand the credentialsId parameter

   In the git step, credentialsId specifies which Jenkins stored credential to use for authentication.

2. Step 2: Identify what 'git-cred-id' means

   'git-cred-id' is the ID of the credential Jenkins uses to access the Git repo securely.

3. Final Answer:

   The Jenkins credential ID used for Git authentication -> Option A

4. Quick Check:

   credentialsId = Jenkins Git credential ID [OK]

Hint: credentialsId links Jenkins to stored Git credentials [OK]

Common Mistakes:

• Confusing credentialsId with repo URL
• Thinking it is branch name
• Assuming it is agent label

4. You added Git credentials in Jenkins but your pipeline fails with authentication errors. What is the most likely cause?

medium

A. The Jenkins agent is offline

B. The Git repository URL is public and does not require credentials

C. The credential ID used in the pipeline does not match the stored credential ID

D. The pipeline syntax is missing the agent any line

Solution

1. Step 1: Check the error cause

   Authentication errors usually mean Jenkins cannot find or use the correct credentials.

2. Step 2: Verify credential ID usage

   If the pipeline uses a credential ID that does not match any stored credential, authentication fails.

3. Final Answer:

   The credential ID used in the pipeline does not match the stored credential ID -> Option C

4. Quick Check:

   Credential ID mismatch = auth error [OK]

Hint: Match pipeline credentialId exactly with stored ID [OK]

Common Mistakes:

• Ignoring credential ID mismatch
• Blaming public repo for auth errors
• Assuming agent offline causes auth errors
• Missing agent line causes auth errors

5. You want to use SSH keys stored as Jenkins credentials to access a private Git repo in a pipeline. Which credential type should you add in Jenkins to support this?

hard

A. SSH Username with private key

B. Secret text

C. Username with password

D. Certificate

Solution

1. Step 1: Identify credential types for Git SSH access

   SSH access requires a private key and username, so Jenkins must store these as credentials.

2. Step 2: Choose the correct Jenkins credential type

   Jenkins provides 'SSH Username with private key' to store SSH keys for Git authentication.

3. Final Answer:

   SSH Username with private key -> Option A

4. Quick Check:

   SSH keys = SSH Username with private key [OK]

Hint: Use SSH Username with private key for Git SSH access [OK]

Common Mistakes:

• Using username/password for SSH key access
• Choosing secret text which is for tokens
• Selecting certificate which is for SSL