Jenkins Jenkins Agents and Distributed Builds 2

Question 1

What is an inbound (JNLP) Jenkins agent?

Accepted Answer

An agent that initiates the TCP connection outward to the controller (agent connects to Jenkins)

Answer

An inbound or JNLP agent initiates the connection from the agent to the controller, which is useful when the controller cannot reach the agent directly.

Question 2

What is the advantage of using Docker containers as Jenkins agents?

Accepted Answer

They offer clean, isolated, and reproducible build environments that are discarded after each build

Answer

Docker agent containers provide a clean, isolated environment for each build, ensuring reproducibility and preventing dependency pollution between builds.

Question 3

What is the purpose of the 'Node' block in a Scripted Pipeline?

Accepted Answer

Allocates an executor on a specified agent to run a block of pipeline code

Answer

In Scripted Pipeline, the `node` block allocates an executor on a matching agent and wraps the code that should run in that agent's workspace.

Question 4

How can you limit which jobs run on a specific Jenkins agent?

Accepted Answer

By using labels on the agent and specifying those labels in job configurations

Answer

Labels assigned to agents are matched by job configurations or pipeline `agent` directives to control which jobs run on which agents.

Question 5

What happens to an agent's workspace after a build completes by default?

Accepted Answer

It persists on the agent filesystem for the next build of the same job

Answer

By default, Jenkins keeps the workspace on the agent between builds to enable faster incremental builds by reusing previously checked-out files.

Jenkins Practice Test

Jenkins Practice Test

Jenkins Jenkins Agents and Distributed Builds 2