Blog

Before we provide TeamCity or Octopus Deploy training to our customers, we have to launch a number of identical virtual machines for the candidates. All of the required software must be installed (TeamCity, Octopus Deploy, Sql Server etc) on the machines, and they must be identical to each other. A customer asked how they could do this in Azure, so we put together some PowerShell, an ARM template and this post to help automate their process.

With more and more organisations starting to implement devops automation to make use of cloud infrastructure and services, more consideration needs to be given to content management systems that rely heavily on a cache for performance in order to keep content in sync across a dynamic number of nodes. With the introduction of flexible load balancing in Umbraco 7.3+ this has become much easier, but can this be achieved in earlier versions?

Stamping assemblies with some form of version number is incredibly useful when trying to tie a binary back to it's source code commit. When using standard centralised source control systems this is a relatively simple process as each commit has an incremental change set number generated by the server and TeamCity exposes this as an internal variable %build.vcs.number%, but with distributed version control systems this is a little more complicated.