Git repository configuration in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Git Plugin: Repository URL Validation

You configure a Jenkins job with the Git repository URL: https://github.com/example/repo.git. What will be the output of Jenkins when it tries to clone this repository if the URL is incorrect or unreachable?

A ERROR: Failed to connect to repository: https://github.com/example/repo.git

B SUCCESS: Repository cloned successfully

C WARNING: Repository URL is deprecated but cloned

D INFO: Repository URL not specified

💡 Hint

Think about what Jenkins reports when it cannot access the Git repository.

If the Git repository URL is incorrect or unreachable, Jenkins will show an error indicating failure to connect to the repository.

❓ Configuration

intermediate

Jenkins Git Plugin: Specifying Branch to Build

In Jenkins Git plugin configuration, which syntax correctly specifies to build only the develop branch?

A refs/heads/master

B refs/tags/develop

C refs/remotes/origin/develop

D refs/heads/develop

💡 Hint

Branches are referenced under refs/heads/ in Git.

The correct syntax to specify a branch in Jenkins Git plugin is refs/heads/branch-name. So for the develop branch, it is refs/heads/develop.

🔀 Workflow

advanced

Jenkins Pipeline: Git Checkout with Credentials

You want to checkout a private Git repository in a Jenkins pipeline using stored credentials with ID git-creds. Which pipeline snippet correctly performs this checkout?

A checkout scm

B checkout([$class: 'GitSCM', branches: [[name: 'refs/heads/main']], userRemoteConfigs: [[url: 'https://github.com/private/repo.git', credentialsId: 'git-creds']]])

C git url: 'https://github.com/private/repo.git', branch: 'main'

D git credentialsId: 'git-creds', url: 'https://github.com/private/repo.git'

💡 Hint

Using checkout with GitSCM class allows specifying credentials explicitly.

The checkout step with GitSCM class and userRemoteConfigs specifying credentialsId is the correct way to checkout a private repo with credentials in Jenkins pipeline.

❓ Troubleshoot

advanced

Jenkins Git Plugin: Resolving 'No credentials specified' Error

A Jenkins job fails with the error: ERROR: No credentials specified when trying to clone a private Git repository. What is the most likely cause?

A The Jenkins job configuration does not specify any credentials for the Git repository

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

C The Git plugin is not installed in Jenkins

D The repository branch name is incorrect

💡 Hint

Think about what Jenkins needs to access private repositories.

If Jenkins tries to clone a private repository without credentials configured, it will fail with 'No credentials specified' error.

✅ Best Practice

expert

Best Practice for Jenkins Git Polling Configuration

Which Jenkins Git plugin polling configuration is best to minimize unnecessary builds while ensuring changes are detected promptly?

A Disable polling and rely only on manual builds

B Poll SCM every minute with <code>* * * * *</code> and disable shallow clone

C Poll SCM every 5 minutes with <code>H/5 * * * *</code> and use shallow clone

D Poll SCM once daily with <code>H H * * *</code> and use shallow clone

💡 Hint

Balance frequency and resource usage for polling.

Polling every 5 minutes with a hashed schedule (H/5) reduces load and avoids all jobs polling simultaneously. Using shallow clone speeds up the clone process.