Instance Health and Capacity Check
A 3-step recipe with Jenkins. We can help you get access.
Recipe · 3 steps
Instance Health and Capacity Check
with Jenkins · Continuous Integration Management
Check that a Jenkins controller is accepting work and has executor capacity.
- Read the top-level Jenkins resource for its mode, whether it is quieting down ahead of a restart, and how many executors it advertises.
- List the connected build agents and their offline state, so a controller with no usable executors is caught before builds are queued against it.
- Read the build queue to measure how many items are waiting and why, which distinguishes a saturated instance from a blocked one.
What you'll need to have ready
- depth: Optional depth for expanding nested objects in the agent listing. Defaults are usually sufficient; raise only when more detail is needed.
For your developer
Arazzo workflow jenkins:instance-health-check, 3 operations: getJenkinsInfo → listComputers → getQueue. Specs on APIs.io.