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.