teamcity

I am on Windows and trying to run multiple (currently two) instances of TeamCity on the same server. I chose not to install the Windows services and instead run the server via runAll.bat start command. When I ran the installer I chose different ports, names and paths for each one. The first server starts successfully, but the second one does not - I see the tomcat window showing up, but it's gone after a while, though the build agent window stays. Here's some output: c:\Tools\TeamCity\bin>runAll.bat start starting TeamCity server and agent... Using CATALINA_BASE: "c:\Tools\TeamCity\bin\.."

I've setup build configuration in TeamCity with 3 steps: Build solution Do unit tests Upload artifacts to FTP For FTP uploading I've used FTPUpload plugin, taken from http://teamcityrunners.codeplex.com/ . Folder to upload was set to absolute path: %userprofile%\.BuildServer\system\artifacts\%env.TEAMCITY_PROJECT_NAME%\%env.TEAMCITY_BUILDCONF_NAME%\%env.BUILD_NUMBER%\ According to build log, artifacts publishing take place only after all steps have been completed. Is it possible to configure TeamCity to publish artifacts after certain build step? We do something similar for one of my projects.

I added a self-signed certificate to my Teamcity BuildServer to introduce https support so that it can now be accessed at https://ServerUrl:8443 (More details about how here ) The result was that I was able access the server via https, but my build agent was now disconnected. How to fix this? The build agent works as a client to the build server and communicates with it using http/https, and it turns out that when you add a self-signed certificate the build agent does not accept it. I needed to Let the build agent know the new path for communicating with the server Let the build agent know

I'm trying to use assembly info patcher to create a version number something like: 1.2.3.1a3c19e where the last bit is the git short hash. I've tried using a powershell script build step to create the short hash (as I cant find a variable that has it) and adding this to a system variable but this build step appears to run after assembly info patcher, so isn't much use. If you want to write this to the Assembly Info field it can be done, but it requires a separate build configuration to generate the build number. The sole purpose of this step is to create the build number that has the hash

In TeamCity is there an easy way to get a variable for the current date in the format MMdd (eg 0811 for 8-Aug)? My google-fu did not turn up an existing plugins. I looked into writing a plugin, but not having a jdk installed, that looks time consuming. Bilal The Groovy Plugin for TeamCity provides build start date/time properties: Provides build properties: system.build.start.date / env.BUILD_START_DATE system.build.start.time / env.BUILD_START_TIME This blog post has installation / configuration instructions for the Groovy plugin, as well an example of customizing the date/time format. This

Continuous integration concept has just been integrated in my team. Assume we have an integration branch named Dev . From it derived 3 branches, one for each specific current project : Project A Project B Project C First, Teamcity is configured on a dedicated server and it goals is : Compiles and launches unit and integration tests from versioned sources from each branch including Dev Then, of course, each project branch (A,B and C) must be tested in a cloned production environment so that UAT can be carried out. But I wonder what frequency should we deploy on? Everytime a source code changes

I'm having a few problems breaking out an MsBuild package+deploy command into two separate commands. (I need to do this to pass additional parameters to MsDeploy). The command that works fine looks like this: msbuild "src\Solution.sln" /P:Configuration=Deploy-Staging /P:DeployOnBuild=True /P:DeployTarget=MSDeployPublish /P:MsDeployServiceUrl=https://192.168.0.1:8172/MsDeploy.axd /P:DeployIISAppPath=staging.website.com /P:AllowUntrustedCertificate=True /P:MSDeployPublishMethod=WmSvc /P:CreatePackageOnPublish=True /P:UserName=staging-deploy /P:Password=xyz The separated packaging command looks

I'm looking to set up a TeamCity server for continuously building a .NET web application. I already have hosting, so I don't want to get a whole new hosting account such as AppHarbor. I don't maintain my own physical server, nor do I want to. I also don't want to have to pay $50 or more per month for an entire dedicated Windows machine, just to host TeamCity. I really don't care if it's slow and on a shared machine, as it's just continuous build which will be running in the background. I'll want to have the outputs automatically deployed to a server of my choice through FTP. Is there anyone on

I've read a handful of posts (see references below) and have yet to find a guide on best practices that is specific to my tech stack. The goal: Create a single NuGet package targeting multiple .NET frameworks built from a single .csproj file via TeamCity using MSBuild and NuGet. The constraints: Pull the code from the VCS only once. All compiled assemblies should be versioned the same. Single .csproj (not one per target framework). I have two approaches in mind: Create a single build configuration. It would contain three build steps: compile .NET 3.5, compile .NET 4.0, pack with NuGet. Each