Is it possible to configure the TeamCity build agent only to run assemblies with a specific parameter dependency?

Question

I have a TeamCity build agent installed on a machine that is theoretically designed to run dynamic security checks, and I don’t want it to do anything else (i.e. it starts searching for duplicates).

With the exception of creating custom agent configuration properties and then setting up build agent dependencies (which, strictly speaking, I should probably do anyway) or setting up the agent only to run selected configurations, is there any way to avoid this? Both of these approaches require additional assembly-based customization for each assembly.

In an ideal world, I would like to tell the agent that he will ever run assemblies that match a specific agent dependency. Is this possible, or am I coming to him from the wrong direction?

Answer 1

I am afraid that TeamCity does not provide a way to indicate that the agent can only run configurations with a specific property (and not run other configurations).

Thus, there are only two ways to specify agents: either with agent requirements, or with agent configuration only to run selected configurations.

You could probably try to make some changes to your build configuration properties, since all build configuration settings / properties are stored in XML files on disk.

Answer 2

In current versions of TeamCity (for example, 8.1), you can only create a pool for your security machine and assign only one computer to this pool, remembering to remove it from other pools.

You can then assign a security project to this pool. This should solve your problem.