#TEAMCITY DEPLOYMENT HOW TO#
#TEAMCITY DEPLOYMENT INSTALL#
#TEAMCITY DEPLOYMENT SERIES#

In order for OctopusDeploy to access the deployment packages they need to be published to a NuGet feed that the OctopusDeploy server can access. Publishing the package to a NuGet feed so OctopusDeploy can access it

PowerShell or another scripting language (if you need more flexibility you can create a custom script to run that will package up the files).

nuspec file then it’s easy to package that up and automatically get it as an artifact by using TeamCity’s NuGet Pack step)

TeamCity NuGet Pack step (if you are using a custom.

#TEAMCITY DEPLOYMENT INSTALL#

OctoPack (if you install OctoPack into your project then it’s dead easy to get the NuGet package - you can install the plugin to invoke it or pass through /p:RunOctoPack=true to MSBuild when you build your solution/project if using.OctopusDeploy uses the NuGet package format to wrap up deployments there are a number of ways you can generate the NuGet package in TeamCity: We wouldn’t always use OctopusDeploy exclusively, but it’s definitely a tool worth having a good understanding of to use judiciously because it can make your life a lot easier. It comes with plugins that make using it with TeamCity a breeze.It is possible to do the same things with MsDeploy, but it is more complex to do.It gives you a lot more flexibility around performing deploy-time actions out-of-the-box and makes it easier to do build once packages.Visualising the deployment pipeline is much easier in OctopusDeploy, which is great when you are trying to get non-technical product owners involved in deployments.

For instance, if you need to perform database migrations then deploy multiple websites and a background worker together then OctopusDeploy makes this easy.

If you are coordinating complex deployments then OctopusDeploy takes care of managing that complexity and the specification of the deployment process in a manageable way (that would start to get complex with TeamCity).

NET community so it’s hard not to notice it - it’s worth looking at it to see what it does

Curiosity OctopusDeploy is getting a lot of attention in the.

There are a number of reasons we have been looking at it: Lately, we have also been experimenting with combining TeamCity with another tool to take care of the deployments: OctopusDeploy.

#TEAMCITY DEPLOYMENT SERIES#

This is one of the reasons we created this blog series we loved how powerful TeamCity is out of the box and wanted to expose that awesomeness so other people could experience what we were. If you can have a single tool to create your deployment pipeline and include continuous integration as well as deployments then there are obvious advantages in terms of simplicity of configuration and management (single set of project definitions, user accounts and permissions, single UI to learn, etc.).

#TEAMCITY DEPLOYMENT HOW TO#

How to choose your deployment technology.Git push (Windows Azure Web Sites Web Jobs).TeamCity deployment pipeline (part 3: using OctopusDeploy for deployments).TeamCity deployment pipeline (part 2: TeamCity 8, build once and UI tests).TeamCity deployment pipeline (part 1: structure).

This post is part of a blog series jointly written by myself and Matt Davies called Maintainable, large-scale continuous delivery with TeamCity: Maintainable, large-scale continuous delivery with TeamCity series This post outlines how using OctopusDeploy for deployments can fit into a TeamCity continuous delivery deployment pipeline.

Teamcity deployment