Maintainable, large-scale continuous delivery with TeamCity Blog Series

I’ve been a ardent supporter of continuous delivery┬ásince I first learnt about it from a presentation by┬áMartin Fowler and Jez Humble. At the time I loved how it encouraged less risky deployments and changed the decision of when/what to deploy from being a technical decision to being a business decision.

I personally think that embracing continuous delivery is an important intermediate step on the journey towards moving from technical agility to strategic agility.

This post was first written in August 2012, but has since been largely rewritten in February 2014 to keep it up to date.

This post forms the introduction to a blog series that is jointly written by myself and Matt Davies.

  1. Intro
  2. TeamCity deployment pipeline
  3. Deploying Web Applications
    • MsDeploy (onprem and Azure Web Sites)
    • OctopusDeploy (nuget)
    • Git push (Windows Azure Web Sites)
  4. Deploying Windows Services
    • MsDeploy
    • OctopusDeploy
    • Git push (Windows Azure Web Sites Web Jobs)
  5. Deploying Windows Azure Cloud Services
    • OctopusDeploy
    • PowerShell
  6. How to choose your deployment technology

Continuous Delivery with TeamCity

One of the key concepts in continuous delivery is the creation of a clear deployment pipeline that provides a clear set of sequential steps or stages to move software from a developer’s commits to being deployed in production.

We have been using TeamCity to develop deployment pipelines that facilitate continuous delivery for the last few years. While TeamCity is principally a continuous integration tool, it is more than adequate for creating a deployment pipeline and comes with the advantage that you are then using a single tool for build and deployment.

We have also tried combining TeamCity with other tools that are more dedicated to deployments, such as OctopusDeploy. Those tools provide better deployment focussed features such as visualisation of the versions of your application deployed to each environment. This approach does create the disadvantage of needing to rely on configuring and using two separate tools rather than just one, but can still be useful depending on your situation.

There are a number of articles that you will quickly come across in this space that give some really great advice on how to set up a continuous delivery pipeline with TeamCity and complement our blog series:

Purpose of this blog series

The purpose of this series is three-fold:

  • Document any findings that myself and Matt Davies have found from implementing continuous delivery pipelines using TeamCity that differ from the articles above;
  • Outline the techniques we have developed to specifically set up the TeamCity installation in a way that is maintainable for a large number of projects;
  • Cover the deployment of Windows Services and Azure Roles as well as IIS websites.

Our intention is to build of the work of our predecessors rather than provide a stand-alone series on how to set up continuous delivery pipelines with TeamCity.

Other options

TeamCity is by no means the only choice when it comes to creating a deployment pipeline. Feel free to explore some of the other options:

14 Replies to “Maintainable, large-scale continuous delivery with TeamCity Blog Series”

    1. I certainly am mate. The next post is half finished in my drafts folder. I’ve had a busy few weeks so I haven’t had an opportunity to complete it. I’ll try and get the next one out this week ­čÖé

      1. Not continues series? :'(

        Deploying Windows Services
        Git push (Windows Azure Web Sites Web Jobs)

        Deploying Windows Azure Cloud Services

  1. Any chance you could skip to part 7, Deploying Windows Services via Msbuild (although I can see that you might need to cover part 6). In this day and age of OWIN Http micro-services, getting Windows Services deployed is more important that ever.

    1. Hi Harry,

      Thanks for the feedback. Matt and I have recently gotten together to prioritise the various things we get up to because we tend to get a little sidetracked. This blog series came out quite high in the list so expect to see some more activity in the next few months ­čÖé


  2. Hey,

    Just stumbled onto this blog post series, and I will be reading through the first three in due course, but would be especially interested in some of the later articles. Hope you guys get a chance to complete the series.



    1. Thanks Gary!

      We definitely will finish the series at some point (promise). As per my last comment – this is still high on our todo list, but not quite at the top yet ­čÖé

Leave a Reply

Your email address will not be published. Required fields are marked *