Can Teamcity prefer a given agent?
We have TeamCityhttp://www.jetbrains.com/teamcity/?fromServer Enterprise 7.0 (build 21241), with three agents connected. Most of our projects can run on two of the agents (A and B), while some projects must have one of these agents to build (A). Is there a way of configuring TeamCity to prefer B for projects that can run on both A and B? It's pretty annoying when A is taken by some project that CAN run on B, when a project that needs A is waiting to build.
Please sign in to leave a comment.
Hi
You can set Run selected configurations only option for agent A, and reserve the agent for specific builds only.
Or use Agent Pools if there are many build configurations within the project.
No, we don't want to reserve one of the agents for some builds, that would only lead to the same problem, but for the other projects. A project that can run on both A and B will have to wait, even though A is free - just because some other project is building on B.
Prefer one server, but be able to run on both. Thats the sweet spot!
Johnny,
There is no feature to "prefer" an agent so far.
Related feature request is filed as TW-1528.
Thanks, hopefully it'll be implemented sometimes soon - it would really smooth things out a lot!
I also wonder can teamcity be configured in the way, that build configurations would prefer agent, that already built this configuration. It can increase speed for cases when docker builds something one one agent and after that same build gets other agent and receives cache miss.
HI guys,
This feature was implemented by a third party as a plugin, described in the comments here: https://youtrack.jetbrains.com/issue/TW-29234, available here: https://plugins.jetbrains.com/plugin/9290-agent-priority