Skip to content
Latchkey

TeamCity "No enabled compatible agents" for a build configuration in CI

TeamCity compared the build configuration requirements against every connected, enabled agent in the assigned pools and none matched. The build stays queued until a compatible agent appears, or the requirement is corrected.

What this error means

A build sits in the queue and the "Compatible Agents" tab shows "No enabled compatible agents can run this build". Hovering an incompatible agent lists the unmet requirement.

TeamCity
No enabled compatible agents can run this build.
Incompatible agents: Agent-1 (Unmet requirement: env.JDK_17 exists),
Agent-2 (Unmet requirement: teamcity.agent.jvm.os.name contains Linux)

Common causes

A build requirement no agent satisfies

An explicit requirement (an env. variable, a tool path, or an exists/contains condition) is not met by any agent in the assigned pools, so all are marked incompatible.

The configuration is assigned to the wrong agent pool

The project is attached to a pool that contains no agent with the needed capability, while a suitable agent lives in a different pool.

How to fix it

Read the unmet requirement and align it

  1. Open the build configuration, go to Agent Requirements, and read each "Unmet requirement" line.
  2. Either add the missing capability to an agent (install the tool, set the env. parameter) or relax the requirement to one an agent actually reports.
  3. Trigger the build again and confirm the Compatible Agents tab now lists an agent.
buildAgent.properties
# example unmet requirement to satisfy on the agent
# add to <agent>/conf/buildAgent.properties
env.JDK_17=/opt/jdk-17

Assign the configuration to a pool that has a matching agent

In Administration, move the project or build configuration to the agent pool that contains an agent reporting the required capabilities.

How to prevent it

  • Base requirements on capabilities agents actually report, not on assumptions.
  • Keep tool versions consistent across agents in a pool so requirements match everywhere.
  • Review agent pool assignment when a new build configuration is added.

Frequently asked questions

What causes ""No enabled compatible agents""?
An explicit requirement (an env. variable, a tool path, or an exists/contains condition) is not met by any agent in the assigned pools, so all are marked incompatible.
How do I fix "No enabled compatible agents"?
Read the unmet requirement and align it

Related guides

References

Latchkey auto-heals failures like this one - detected, fixed, and retried without you. Start free → 30-day trial · No credit card