ERROR: No such node during agent label resolution

Jenkins Node Labeling and Agent Availability

In low-traffic CI environments, infrastructure costs are often managed by terminating idle agents. However, when a job is configured with a specific node label that is not currently active in the cluster, Jenkins may trigger a failure condition rather than waiting for a resource to become available.

The core Jenkins controller does not natively provide a configuration flag to automatically provision a missing node based solely on a label request. This creates a conflict between cost-saving termination policies and build reliability, as jobs referencing missing labels may abort immediately.

Assuming a standard Jenkins LTS installation, there is uncertainty regarding the native behavior of the scheduler when labels are missing versus when nodes are simply offline.

• Does Jenkins provide a native mechanism to trigger on-demand node creation when a label match is not found?
• Is there a documented way to differentiate between a permanently missing node label and a temporarily unavailable agent to prevent immediate build failure?