Octopus supports TeamCity

Automated deployments from TeamCity

Octopus is the easiest way to automate complex application deployments as part of a JetBrains TeamCity build configuration.

Download Octopus + TeamCity guide

TeamCity is a powerful build server. It works with any source control system you might have, and it has built-in tasks for compiling and running tests for any common programming language. It can build your Visual Studio solution, run your NUnit/MSTest unit tests, collect .NET code coverage data, and perform code analysis.

Scroll through the extensive list of built in tasks, though, and you'll notice a gap. Where are the tasks to deploy the software once it is built? Where are the tasks to configure IIS, or install a Windows service? Where are the tasks to change configuration files depending on the environment? On the surface, TeamCity is a continuous delivery tool, but read through the details and you'll find that deployment is limited to calling a big script that you write yourself. It's up to you to figure out the nitty gritty deployment details.

Just like TeamCity makes build automation easy, Octopus Deploy makes deployment automation easy.

TeamCity builds the code and runs tests, while Octopus takes care of:

  • Distributing applications to all the remote machines, securely
  • Environment-specific configuration, like connection strings
  • Configuring IIS sites and installing Windows Services
  • Doing all of the above across many machines in parallel

Learn more about connecting TeamCity with Octopus and our TeamCity plugin.

Building and pushing packages

Have TeamCity compile your code, run the tests, and build a package ready for Octopus to deploy. You can push the package directly to Octopus, or have Octopus fetch it from the TeamCity NuGet feed.

Build and push packages with TeamCity

Promote and deploy releases

Create releases in Octopus once the TeamCity build completes. Automatically deploy the release to a Dev environment, or chain TeamCity builds to deploy to a Test environment, run automated integration tests, then promote to staging or production.

Create your release in Octopus once your TeamCity build is complete and fully tested

Fail the build if the deployment fails

Output from the Octopus deployment can appear in the TeamCity build log, and you can have TeamCity fail the build if the deployment in Octopus fails.

TeamCity and Octopus logs are in sync with each other

End-to-end traceability

Commit packages with proper versioning and trace back to exactly where it came from.

Package steps

Create your package from a single step inside TeamCity

Plugin or Command Line

Use our first-class plug-in or simply call our command-line tools.