If anyone’s going through an installation and configuration of these tools, here’s the steps we carried out, and some lessons learned along the way. The harder part came later: how do we configure those tools in the best way to support our development workflow? As we configured the tooling, this was also an opportunity to look again at our processes and identify ways in which the new tools allow us to improve quality.

In some senses coming to that decision was the easy part. We went through a 2-month period of thinking deeply about our requirements and trialling different software in order to land at the tools which we felt were the correct long-term fit: Git, TeamCity and Octopus Deploy. Around 18 months ago, we went through a significant shift in deployment pipeline tooling within our agency.Īfter 7 years of using an on-premise Team Foundation Server (TFS) instance for version control and builds, integrating with MSDeploy for deployment, I realised we needed to be doing more within our build processes, and there were better tools available for our needs.

Download teamcity octopus