teamcity

I am trying to do "continuous integration" with TeamCity. I would like to label my builds in a incremental way and the GUID provided by the VCS is not as usefull as a simple increasing number. I would like the number to actually match the revision in number in Mercurial. My state of affairs: Mercurial info: I would like the build to be labeled 0.0.12 rather than the GUID. Would someone be so kind and save me hours of trying to figure this out ? As Lasse V. Karlsen mentioned those numerical revision numbers are local-clone specific and can be different for each clone. They're really not

We are migrating to .NET 4 and very interested in implementing new Design By Contract capabilities. As we know Code Contract engine requires installation of Code Contract addin and VS Ultimate or Premium (for static checking). Here is my questions: Can I use code contract rewriting without installing VS on CI build Server (TeamCity)? Is there any msbuild tasks to execute Contract checking? Do you use Code Contract's validation with CI builds? Judah Gabriel Himango Can I use code contract rewriting without installing VS on CI build server (TeamCity)? Yes. Install CodeContracts on the build

I have some XML that looks something like this: <?xml version="1.0" encoding="utf-8"?> <XmlConfig instancetype="XmlConfig, Processing, Version=1.0.0.0, Culture=neutral"> <item> <key>IsTestEnvironment</key> <value>True</value> <encrypted>False</encrypted> </item> <item> <key>HlrFtpPutDir</key> <value>C:\DevPath1</value> <encrypted>False</encrypted> </item> <item> <key>HlrFtpPutCopyDir</key> <value>C:\DevPath2</value> <encrypted>False</encrypted> </item> .... </Provisioning.Lib.Processing.XmlConfig> In TeamCity I have many system properties: system.HlrFtpPutDir H:\ReleasePath1 system

We are a mostly MS shop at work doing .NET LOB development. We also use MS Dynamics for our CRM app... all the devs are currently using VS/SQL Server 2008. We also use VSS, but everyone hates it at work and that is quickly on its way out. We are begining our initiative for TDD implementation across the team (~dozen ppl). I've gotten TeamCity setup and have my first automated builds running succesfully using the 2008 sln builder and also using SVN that a co-worker had setup who is doing the source control analysis. When demoing to managament, I think they started to buy into my snake oil and

We are a Java shop looking for a CI tool to use. Both Hudson and Teamcity seem to be free but Teamcity seems slicker and with more support. I was wondering why one would still use Hudson and if anyone could provide any argument for/against either? Nat Team City is by far and away the best CI server out there. Its killer feature for me is the tight integration with IDEs (IntelliJ, Eclipse and VisualStudio). It can show you, for example, when a file you're editing in the IDE becomes out of date, who changed it and what they changed. You can commit from the IDE to the CI server, run the comile

I'm trying to deploy a windows service using an MSBuild script that runs a Powershell command. The MSBuild script deploys the files I need and the PowerShell script will uninstall and reinstall the windows service using this command: Invoke-Command -ComputerName IPAddressHere -FilePath "C:\theScriptFileName.ps1" -credential "TheUserName" Using an IP address (which I need to because of different domains) I need to use credentials. The problem is that it prompts for a password, which won't work for TeamCity's automation. I know I can save the credentials into a variable so that the prompt won't

I've run into a bit of a catch-22 here. I'm using NuGet and TeamCity. I've tried doing NuGet pack with the nuspec file, and I've also tried with the csproj file. Each has its own issue: In TeamCity, if I use the nuspec file with NuGet pack , the $version$ token, in the nuspec file, doesn't get updated. If I change TeamCity to NuGet pack using the csproj file, the $version$ token gets updated, however the resulting package only has the EXE in it, and all of the dependent assemblies are missing. This problem doesn't happen when using the nuspec file. Is there a way to get the best of both worlds

Given I have Teamcity job with Git VCS root with default branch which can be changed with branch-name parameter: When I e.g. set branch-name to develop in admin screen, go back to build configuration home and run custom build where I change branch-name parameter to master then I get: Why is that? What should I change, so that I don't get this message and I can change branch when running custom build? The reason for this is I want to build and deploy software artifacts from any feature branch the Teamcity has an opportunity for monitoring the branches and runs built to custom branch. Firstly,