teamcity

I've got an asp.net mvc deployment package that I'm trying to build with team city. The package builds without any problems, but the bin folder contains file that are not needed (and cause the site to fail when present). If I build the same package from visual studio the additional files are not present. The additional files are: Microsoft.VisualBasic.Activities.Compiler.dll mscorlib.dll normidna.nlp normnfc.nlp normnfd.nlp normnfkc.nlp normnfkd.nlp System.Data.dll System.Data.OracleClient.dll System.EnterpriseServices.dll System.EnterpriseServices.Wrapper.dll System.Transactions.dll What can

I'm trying to deploy one of the web projects in my solution to a server. I am using msbuild on TeamCity like so: msbuild MySolution.sln /t:WebSite:Rebuild /p:DeployOnBuild=True /p:PublishProfile=Prod ... However, when I run it, msbuild still tries to build my WebService project, even though my WebSite project does not depend on it (but it does depend on a Services project also in the solution). How do only publish one project, aka just WebSite ? I have also tried building the project file using msbuild WebSite/WebSite.csproj /p:DeployOnBuild=True ... but it then complains that it can't restore

I have a TeamCity server setup to do my CI builds. I'm building and testing a C# solution and running some custom MSBuild tasks. One of these tasks is printing a warning in my build output... MSBuild command line parameters contains "/property:" or "/p:" parameters. Please use Build Parameteres instead. I don't understand what this means or how to remove it. It doesn't Google well (with or without the typo). I ran the task from the command line (with /verbosity:diagnostic ) and it doesn't appear, so I believe it's a TeamCity message. The MSBuild task is <Target Name="InstallDb"> <MakeDir

I'm wondering how to select the branch to build against using Team City 8.1. My VCS root (Git) is set to Default: "master" and Branch specifications are +:refs/heads/develop +:refs/heads/feature/* +:refs/heads/hotfix/* +:refs/heads/master +:refs/heads/release/* I have a CI build set up that automatically builds anything that is checked in, which is working exactly how I want. What I'd like to do is create a scheduled QA build/deployment against the "develop" branch. I see that if I click the ellipsis next to the run button, I can choose the branch on the "Changes" tab, but I'm unable to

We have several build machines, each running a single TeamCity build agent. Each machine is very strong, and we'd like to run several build agents on the same machine. Is this possible, without using virtualization ? Are there quality alternatives to TeamCity that support this? CrazyCoder Yes, it's possible : Several agents can be installed on a single machine. They function as separate agents and TeamCity works with them as different agents, not utilizing the fact that they share the same machine. After installing one agent you can install additional one, providing the following conditions

I have a TeamCity 7 Build Configuration which is pretty much only an invocation of a .ps1 script using various TeamCity Parameters. I was hoping that might be a simple matter of setting: Script File Script File %system.teamcity.build.workingDir%/Script.ps1 Script execution mode Execute .ps1 script with "-File" argument Script arguments %system.teamcity.build.workingDir% -OptionB %BuildConfigArgument% %BuildConfigArg2% And then I would expect: if I mess up my arguments and the script won't start, the Build fails if my Script.ps1 script throws, the Build fails If the script exit s with a non- 0

New to TeamCity. I have multiple build steps. Step 3 generates an id that is needed in step 4. What is the best way to pass the id (a string) between step 3 and step 4? The build steps are written in Ruby. Can I set an environment variable? Maria Khalusova Yes, you can set an environment variable in one build step and use it in the following step. You will need to use a service message in your build script as described here http://confluence.jetbrains.net/display/TCD65/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-AddingorChangingaBuildParameterfromaBuildStep to