Jenkins Jenkins CI/CD Integration

Question 1

What is Continuous Integration (CI) in the context of Jenkins?

Accepted Answer

Automatically building and testing code on every commit to catch integration issues early

Answer

CI means automatically building and running tests on every commit so that integration problems are caught early in the development cycle.

Question 2

How does Jenkins typically detect new code changes from a Git repository to trigger a build?

Accepted Answer

Jenkins polls the repository on a schedule or receives a webhook push notification from the Git server

Answer

Jenkins can either poll the SCM on a schedule (checking for changes) or receive a webhook push from GitHub/GitLab when new commits are pushed.

Question 3

What is the purpose of the 'Build Triggers' section in a Jenkins job configuration?

Accepted Answer

To define what events or schedules should automatically start a build

Answer

Build Triggers define the conditions under which Jenkins automatically starts a build, such as webhooks, SCM polling, upstream job completion, or a cron schedule.

Question 4

What Jenkins trigger type uses a cron-like expression to schedule builds at specific times?

Accepted Answer

Build periodically

Answer

The 'Build periodically' trigger uses a cron syntax to schedule builds at regular intervals regardless of code changes.

Question 5

What does 'Poll SCM' trigger do in Jenkins?

Accepted Answer

Checks the source repository on a defined schedule and triggers a build only if changes are detected

Answer

Poll SCM causes Jenkins to check the configured repository on a schedule (using cron syntax) and triggers a build only when new commits are found.

Jenkins Practice Test

Jenkins Practice Test

Jenkins Jenkins CI/CD Integration