TeamCity from JetBrains is a popular continuous integration server that supports a variety of different version control systems and build runners. Octopus Deploy and TeamCity can work together to make automated, continuous delivery easy.
When using Octopus Deploy with TeamCity, TeamCity will usually be responsible for:
- Checking for changes in source control
- Compiling the code
- Running unit tests
- Creating NuGet packages for deployment
While Octopus Deploy will be used to take those NuGet packages and to push them to development, test and production environments.
Integration with TeamCity involves two major parts:
1. Creating the NuGet packages from your applications
2. Optionally, when a build completes, having TeamCity make requests to your Octopus Server to:
(a) Create releases; (b) Trigger deployments and/or (c) Promote releases when a build completes
Installing the plugin
To make integrating with TeamCity easy, a plugin is available from our download page. The plugin is distributed as a ZIP file. To install:
- Download the TeamCity Plugin ZIP file
- Shut down your TeamCity server
- Copy the ZIP file with the plugin to
<TeamCity Data Directory>/plugins
- Start TeamCity server: the plugin files will be unpacked and processed automatically
Creating Octopus-compatible NuGet packages using TeamCity
Octopus requires that you package your applications into NuGet packages, whether or not you are using TeamCity. There are many ways to create Octopus-compatible NuGet packages, but the easiest way is with OctoPack.
When you set up your build configuration in TeamCity, use either the MSBuild runner or the Visual Studio build runner. At the bottom of the runner settings, you'll see some options to run OctoPack during the build:
The OctoPack package version setting should evaluate to a version number with multiple parts (e.g., 1.3.7). It cannot be a single number. You may want to edit the General Settings for your project to ensure that the TeamCity build number uses multiple parts:
With these options selected, NuGet packages will automatically be created using the version number of the current build. OctoPack will ensure that these packages appear in the artifacts tab of TeamCity:
Consuming the TeamCity NuGet feed in Octopus
TeamCity 7 and up can act as a NuGet repository. You can enable this by going to the Administration->NuGet Settings page, and enabling the inbuilt NuGet server. Any build artifacts ending with
.nupkg will automatically be served as NuGet packages, which Octopus can consume.
To connect Octopus to your TeamCity server, add the TeamCity authenticated feed URL to your NuGet settings in Octopus on the External Feeds tab under the Library page.
Once added, the TeamCity feed will appear in the NuGet feed list:
You can use the Test link to make sure that the NuGet package is available, before creating your Octopus project:
Creating and pushing packages from TeamCity to Octopus
Triggering deployments from TeamCity
The Octopus TeamCity plugin comes with these custom build runners:
- Octopus Deploy: Push Packages (Octopus 3.3 and TeamCity plugin 3.3.1 or newer)
Push packages to the Octopus Deploy built-in repository, optionally using the TeamCity zip feature to create packages on-the-fly.
- Octopus Deploy: Create Release
Creates a new release in Octopus Deploy, and optionally deploys it to an environment
- Octopus Deploy: Deploy Release
Deploys an existing release to a new environment
- Octopus Deploy: Promote Release
Promotes an existing release from one environment to another.
The plugin is simply a wrapper for Octo.exe, the Octopus command line tool for creating and deploying releases.
The video below is from a webinar hosted by JetBrains in which we demonstrated these features: