GardenCloud & systems

When Jenkins cannot find a command on an agent

Inspect the execution environment rather than assuming the interactive shell and build share a PATH.

A command available in an interactive SSH session may be missing from a Jenkins build. The agent process can start with different environment variables and shell initialization.

The original workaround opened the node’s configuration, enabled environment variables under Node Properties, and supplied:

Name: Path
Value: /home/nhancv/:$PATH

That records the earlier UI example, including its Path spelling. On a case-sensitive environment, Path and PATH are different names. Inspect the actual build environment before choosing the override.

The symptom does not prove that every controller copies its own PATH to every agent. This note was not verified against a new Jenkins installation, and no node configuration was changed.

← Back to the garden