Git plugin configuration in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Git plugin: What is the output of this Jenkins pipeline snippet?

Consider this Jenkins pipeline snippet using the Git plugin to clone a repository. What will be the output in the Jenkins console after running this?

Jenkins

pipeline {
  agent any
  stages {
    stage('Clone') {
      steps {
        git url: 'https://github.com/example/repo.git', branch: 'main'
      }
    }
  }
}

A Cloning into 'repo'...\nChecking out Revision main (refs/heads/main)\nFinished: SUCCESS

B Cloning into 'repo'...\nfatal: remote origin already exists.\nFinished: FAILURE

C ERROR: Repository not found.\nFinished: FAILURE

D Cloning into 'repo'...\nChecking out Revision develop (refs/heads/develop)\nFinished: SUCCESS

💡 Hint

The branch specified is 'main', so the checkout will be for 'main'.

The git step clones the repository URL and checks out the specified branch 'main'. The output shows cloning and checking out 'main' branch with success.

❓ Configuration

intermediate

Git plugin: Which configuration snippet correctly sets credentials for private repo access?

You want Jenkins to clone a private Git repository using stored credentials. Which configuration snippet correctly sets the credentials ID in the Git plugin step?

A git url: 'https://github.com/private/repo.git', credentialsId: 'my-creds-id'

B git url: 'https://github.com/private/repo.git', credentialId: 'my-creds-id'

C git url: 'https://github.com/private/repo.git', credentials: 'my-creds-id'

D git url: 'https://github.com/private/repo.git', credId: 'my-creds-id'

💡 Hint

The Git plugin expects the exact parameter name for credentials.

The correct parameter name is 'credentialsId' to specify stored credentials for Git plugin in Jenkins.

❓ Troubleshoot

advanced

Git plugin: Why does this Jenkins job fail with 'Could not resolve host' error?

A Jenkins job using the Git plugin fails with this error: 'fatal: unable to access 'https://github.com/example/repo.git/': Could not resolve host: github.com'. What is the most likely cause?

A The repository URL is misspelled in the job configuration

B Jenkins server has no internet or DNS access to github.com

C The Git plugin is not installed in Jenkins

D The credentials ID is invalid or missing

💡 Hint

The error indicates a network or DNS problem.

The error 'Could not resolve host' means Jenkins cannot find the github.com server, usually due to network or DNS issues.

🔀 Workflow

advanced

Git plugin: What is the correct order of steps to configure a Jenkins job to poll Git changes?

Arrange these steps in the correct order to configure a Jenkins freestyle job to poll a Git repository for changes.

A 1,2,3,4

B 3,1,2,4

C 1,3,2,4

D 3,2,1,4

💡 Hint

You must first define the repo and credentials before enabling polling.

First add repo URL, then credentials if needed, then enable polling, then set schedule.

✅ Best Practice

expert

Git plugin: Which practice ensures secure and maintainable Jenkins Git configurations?

Which of the following is the best practice when configuring Git plugin in Jenkins for multiple jobs accessing private repositories?

A Create separate credentials for each job with the same username and password

B Hardcode username and password in each job's Git URL

C Use anonymous access for all repositories to avoid credential management

D Store credentials centrally in Jenkins Credentials and reference by ID in jobs

💡 Hint

Centralized credential management improves security and ease of updates.

Storing credentials centrally and referencing by ID avoids duplication and improves security.