Hi,

Not sure if this is a issue or a feature request.

I tried asking this question on the Developer COmmunity forum but got no replies: http://devnet.jetbrains.net/thread/303850


We currently use EC2 build agents with Teamcity 6.0 and it works fine.

But, one of our projects need to have an installer as a build artifact. Well, this installer was built using Visual Studio Setup Project (.vdproj). Long story short, the only way to compile and build the installer is calling devenv.exe (Visual Studio) directly. Thus, I had to install Visual Studio on the Build Agent.

As we have multiple projects running on our TeamCity server, and all of them using the same build agent on EC2, and given that we don't want to have VS installed on the build agent for the other projects, I created a second image on EC2 of a Teamcity Agent with Visual Studio installed on it. Then I created a new cloud profile on Teamcity to use that image.

So now I get to my question:

Given that I have two cloud profiles:


A => Agent without VS insttaled; compatible with all builds configurations
B => Agent with VS installed; compatible with all builds configurations


How do I configure TeamCity to only use cloud profile B with a particular build configuration. i. e. I want that only the "Installer" build configuration for a particular project to use profile B. All others should always use profile A.

I know I can do this explicitly in the Build Agent level but when the instance is terminated I lose this configuration and the next time a instance of cloud profile B is instantiated, it will not have that build compatibility settings. That's why I'm wondering if it's possible to set this at the cloud profile level instead.

Is this possible?