CODEWITHSUNDEEP
configurationbuildteamcity
Troy Hunt
Troy Hunt

Reputation: 20407

Can a TeamCity build agent be configured to only run builds with a particular parameter dependency?

I have a TeamCity build agent installed on a machine which in theory is dedicated to running dynamic security scans and I don't want it doing anything else (i.e. running the duplicates finder).

Short of either creating custom agent configuration properties then customising each build's agent dependencies (which perhaps strictly speaking I should be doing anyway) or configuring the agent to only run selected configurations, is there any way to avoid this? Both of these approaches require additional configuration on a per-build basis either on every single build.

In a perfect world, I'd like to be able to tell the agent to only ever run builds which match a particular agent dependency. Is this possible or am I coming at it from the wrong direction?

Upvotes: 4

Views: 3932

Answers (2)

MichaelRom
MichaelRom

Reputation: 168

In current versions of TeamCity (e.g. 8.1) you can create a pool just for your security machine, and only assign the one machine to that pool, remembering to remove it from other pools.

Then you can assign the security project to that pool. That should solve your problem.

Upvotes: 3

KIR
KIR

Reputation: 5712

I'm afraid TeamCity doesn't provide a way to specify that agent can run only configurations with a specific property (and not run other configurations).

So, there are only two ways to specify agents: either with agent requirements, or with configuring the agent to only run selected configurations.

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

Upvotes: 3

Related Questions