Source code management setup in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Git SCM Plugin: What is the output?

You configured a Jenkins job with Git SCM plugin to clone a repository. The repository URL is correct, but the branch name is set to feature-xyz which does not exist in the remote repo.

What will Jenkins show in the console output when it tries to fetch this branch?

A Cloning repository... Branch feature-xyz checked out successfully.

B Build succeeded without fetching any branch.

C ERROR: Could not find remote branch feature-xyz to clone.

D Warning: Branch feature-xyz is deprecated, using master instead.

💡 Hint

Think about what happens if Jenkins tries to fetch a branch that does not exist.

Jenkins will fail to fetch a branch that does not exist and show an error message indicating the missing remote branch.

❓ Configuration

intermediate

Jenkins Pipeline SCM Configuration Syntax

Which Jenkins Pipeline syntax snippet correctly checks out a Git repository from https://github.com/example/repo.git on branch develop?

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

B git url: 'https://github.com/example/repo.git', branch: 'develop'

C checkout scm: git('https://github.com/example/repo.git', 'develop')

D gitCheckout(url: 'https://github.com/example/repo.git', branch: 'develop')

💡 Hint

Remember the Jenkins Pipeline checkout step syntax for GitSCM.

Option A uses the correct checkout step with GitSCM class and proper branch and URL configuration.

❓ Troubleshoot

advanced

Jenkins Git Credentials Failure Diagnosis

A Jenkins job configured with Git SCM fails with the error: Authentication failed for https://github.com/example/repo.git. The credentials are set as username/password in Jenkins credentials store.

Which is the most likely cause?

A The Git plugin version is outdated and incompatible with GitHub.

B The repository URL is incorrect and does not match the credentials domain.

C The Jenkins server has no internet access.

D The credentials are not linked to the Git SCM configuration in the job.

💡 Hint

Check if the credentials are properly selected in the job configuration.

If credentials are not linked in the SCM configuration, Jenkins cannot authenticate even if credentials exist in the store.

🔀 Workflow

advanced

Jenkins Multibranch Pipeline SCM Behavior

In a Jenkins Multibranch Pipeline job, what happens when a new branch is pushed to the remote Git repository?

A Jenkins ignores new branches until manually added in the job configuration.

B Jenkins automatically detects the new branch and creates a new job for it.

C Jenkins deletes all existing branches and only builds the new one.

D Jenkins triggers a build on the master branch only.

💡 Hint

Think about how Multibranch Pipeline jobs manage branches automatically.

Multibranch Pipeline jobs scan the repository and automatically create jobs for new branches.

✅ Best Practice

expert

Best Practice for Jenkins SCM Polling Frequency

What is the best practice for setting SCM polling frequency in Jenkins to balance build responsiveness and server load?

A Set polling interval to every 5 minutes to catch changes quickly without overloading the server.

B Set polling interval to every 30 seconds for immediate build triggers.

C Set polling interval to once a day to minimize server load.

D Disable polling and rely only on manual build triggers.

💡 Hint

Consider the trade-off between build speed and resource usage.

Polling every 5 minutes is a common balance to detect changes promptly without excessive load.