Eugene on dev

TeamCity and Mercurial Mq Extensions

2012-02-08T08:29:00.001+01:00

In this post I show how to setup Mq patches with TeamCity build. First of all, let's start with basics. I decided to use Mq extension to deal with patches to a opensource library with sources under Mercurial. The goal was to have a build configuration that fetches sources from the library repository, applies patches from patches repository, builds, tests and packages the library. Mq Basics

TeamCity Support for NuGet 1.6

2011-12-15T17:46:00.000+01:00

Today I added tests for compatibility of NuGet plugin for TeamCity with NuGet 1.6 It's nice to say that my plugin for NuGet commandline that I wrote for NuGet 1.4 is still working. All tests are green. I created an issue for NuGet.org v2 feed to provide more easy-to-fetch information about packages in the feed. If you use NuGet, please make sure you on the latest build of the plugin.

NuGet.config Support

2011-12-02T15:42:00.001+01:00

There was an issue for our NuGet in TeamCity plugin support: TW-18927 As it turned out, it's possible to make NuGet use custom folder to store all packages. To do it you need to create NuGet.config file near your .sln file with the following content: Starting from recent builds, NuGet plugin for TeamCity (versions 0.5.x and bundled) will be using this file to

Playing Git

2011-12-02T12:45:00.001+01:00

In this post I describe my pattern of Git usage. My project (NuGet support for TeamCity) contains two main branches called 'v0.5-bugfix' and 'v0.6-bugfix'. 'v0.5-bugfix' branch is targeted for TeamCity 6.5.x. 'v0.6-bugfix' is targeted for TeamCity 7.0 and contains more features. To start a new feature development I first decide if I want this feature to be delivered for 0.5 or 0.6 version.

On-the-fly Code Generation with .NET Expression Trees

2011-11-28T00:35:00.001+01:00

Recently I came to the task to fill a bunch of C# object properties from a Dictionary. There were 10+ fields and I decided to use reflection to avoid writing and supporting dummy code on every object change. So I come up with code like: typeof(DataObject).GetProperties().Where(...).Select(x=>x.SetValue(instance, GetValue(x), null)); Of course this code was not fast. I used Reflection

TeamCity.ServiceMessages Write API

2011-11-15T16:17:00.001+01:00

Today I published TeamCity.ServiceMessages v2.0 package which provides API for generating TeamCity specific service messages. Service messages are described in the documentation page at http://confluence.jetbrains.net/display/TCD7/Build+Script+Interaction+with+TeamCity Introduction Do you know what service messages are? Service Messages are strings in the following format: ##teamcity[hello

TeamCity Service Messages Library for .NET

2011-10-21T12:44:00.000+02:00

Do you know what service messages are? Service Messages are strings in the following format: ##teamcity[hello message='teamcity'] TeamCity uses Service Messages to provide an easy API for a build scripts integration, i.e. build status reporting, artifacts publishing, tests reporting and more. For precise description of the format and service messages usage in TeamCity, take a loot at Build

Changes in NuGet Pack Runner

2011-10-10T08:48:00.001+02:00

I added support for multiple NuGet packages creation in TeamCity "NuGet Packages Pack" build runner: In the "Package Parameters" section I added expanded Specification File section to allow to specify more than one file to create package! Wildcards are supported now. Thanks to the update, you may use one "NuGet Pacakge Pack" runner to create as many packages as you link in one shot.

NuGet Dependency Trigger Update

2011-10-06T15:52:00.001+02:00

Fresh builds of NuGet plugin for TeamCity contains scalability improvements for NuGet Dependency Trigger. (TW-18429) In this blog post I'll describe NuGet Dependency trigger internal implementation. Those are main steps that improved performance: Join all triggers of the same package into one check request Perform checks of many packages inside one NuGet.exe call Allow running more

NuGet Package Publish Runner Security Update

2011-10-04T13:49:00.000+02:00

First implementation of NuGet Package Publish runner contained a bug. In the build log it logged the full commandline to calling nuget.exe process. As it turned out this commandline contained used NuGet.org API key. I fixed the issue on Aug 25-th. Thanks to @hazzik who noticed that TeamCity.CodeBetter.com is running on older version of plugin and thus unveils API keys. On Sunday, 02 October

Automatic NuGet.exe Distribution in TeamCity

2011-10-03T17:00:00.000+02:00

About a month ago I added a NuGet.exe tool selection and distribution support to NuGet plugin for TeamCity. There appeared the NuGet tab in 'Server Configuration' section in Administration. There you can select and download NuGet.CommandLine client to use with TeamCity. Downloaded NuGet Commandline tool will be distributed to all agents automatically. On this tab you can manage available

Selective Publishing of NuGet Packages in TeamCity

2011-09-29T13:07:00.001+02:00

TeamCity NuGet plugin provides a build runner to publish a NuGet package to the feed. It makes it quite easy to make TeamCity create and publish a package from every build. For some reason you may not need to publish every created NuGet package to the feed. In this post I'll describe how one can configure it with TeamCity. To make it work you need to have two build configurations: One

MSBuild Logging Tree

2011-09-08T12:55:00.000+02:00

TeamCity build log provides several view modes. One of my favorite modes is Tree view. I was working hard to improve MSBuild / Visual Studio (sln) build runners logging and fix some issues with it. Starting from TeamCity 7.0 EAP MSBuild / Visual Studio (sln) runners build log tree view is improved and will look like: The main difference to older version is that now all messages are

How to pack agent plugin for TeamCity

2011-09-05T11:51:00.000+02:00

In this post I'll describe how to pack build agent plugins for TeamCity 6.5 or newer. To start, have a look at plugin development page in TeamCity documentation. There you'll find information on how to prepare server-side plugin for TeamCity. Server-side plugin package may contain agent plugin(s). Below you'll find only description of agent-side plugins. TeamCity build agent supports 3 type

NuGet 1.5 and TeamCity

2011-08-31T11:14:00.002+02:00

Today I updated all my NuGet.exe integration tests to run against both NuGet 1.4 and NuGet 1.5. I'm happy to notice, there were no breaking changes in NuGet between 1.4 and 1.5. There was a great post on NuGet support in TeamCity at http://blogs.jetbrains.com/dotnet/2011/08/native-nuget-support-in-teamcity/ We plan to bundle NuGet plugin into forthcoming TeamCity 7.0 EAP builds and you may

NuGet Publish Build Runner

2011-07-22T00:32:00.000+02:00

TeamCity plugin for NuGet support v0.4 is out. In this version I included a new build runner called "NuGet Packages Publish". This build runner helps you to publish (push) NuGet packages to a given feed (custom or default). Publishing of packages is done with help of nuget.exe push command. Build runner settings are the following: Download and Info:For more information, see NuGet plugin home

NuGet for TeamCity plugin BREAKING CHANGE

2011-07-21T17:32:00.001+02:00

I've committed a BREAKING CHANGE to NuGet Plugin for TeamCity. As it turned out, for some databases TeamCity starts throwing data truncation warnings into server logs for too long run type name that could not be saved. Those warnings were caused by NuGet Packages Installer build runner. The only way to fix the issue is to change run type of the build runner to new shorter string. I had to do

TeamCity and NuGet support

2011-07-19T17:38:00.003+02:00

In this blog post I introduce a plugin for TeamCity 6.5 that provides support for NuGet. The plugin provides a NuGet Packages Installer build runner. With help of which you may: Install NuGet packages that were not checked in to the version control, (optionally) Update package dependencies to the most recent ones Installation of packages that were not checked in to version control was also

Collections#syncronized* vs for statement

2011-07-06T09:58:00.000+02:00

As we can see in javadoc (say for 1.6) java.util.Collections#synchronized* methods does not synchronize iterators! This is properly documented in the javadocs of it. As we can see in spec http://java.sun.com/docs/books/jls/third_edition/html/statements.html#14.14.2 java foreach (= enhanced for) statement uses iterator inside. Let's to small check with javac and jad: Here I have a class with a

Agent parameters story

2011-07-01T10:11:00.003+02:00

There are parameters and references in TeamCity. You may use %PARAM_NAME% syntax mostly in all editable build configuration fields to refer to the value of parameter PARAM_NAME. This gives you much power in customizing and reusing. In this post I'll cover build agent side of parameters infrastructure api. On build agent side there are 3 add parameters methods named like: - add*ConfigParameter -

Navigating YouTrack Issues

2011-05-11T18:22:00.003+02:00

I used to use YouTrack to track all issues. Some times I need to open an issue in YouTrack by number. This usually happens if team-mate says me a number or if I see only a issue id without a link. My solution is to crate a small .bat file placed in the system path.Source of my TW.bat:explorer http://www.jetbrains.net/tracker/issue/TW-%1Now to open an issue I do the following:- press WIN + R- type

Debugging build properties

2011-05-06T13:30:00.005+02:00

Do you know what properties were put into a build in TeamCity? For some reason you may need to know that. Adding debug prints/echos in the build is too boring! Starting from TeamCity 6.5 you may find final property values in every build in 'Build Parameters' tab:

Debugging Builds

2011-05-04T17:59:00.006+02:00

In most cases setting up a CI build could be an easy task. But, sometimes things are getting wrong and one may need a debugging. For example, build may fail or misbehave because of lack of files under some folders. To fix the issue you may need to take a look on build files. In some setups this may be hard to do. You may need to connect to remote machines, use different OS, have issue with access

TeamCity code coverage with xunit

2011-04-27T13:57:00.009+02:00

Recently I decided to set up a CI build for a project: https://github.com/hhariri/jsonfxYou may notice that it uses xunit to run tests. My goal was to set up TeamCity build with tests under xunit and code coverage.Hopefully I noticed that xunit supports TeamCity! To make it report tests for TeamCity all you need is to add /teamcity command line argument. Amazing! (I should probably write a plugin

Window/Mono tests running

2011-04-18T23:15:00.004+02:00

I had to debug/fix my .NET application under Linux/Mono. That was nice to find Suse VMWare images just on http://mono-project.com web site. Unfortunately, I failed to compile my project under Mono. C# compiler crashed. So no chance that to develop and debug code. I played a little with Mono packages under Suse, but failed. I mounted samba shared folder under mono and started running tests with