This video explains how to configure the TeamCity build server to create NuGet packages and send the packages to the Octopus package server. Learn where to add the required msbuild parameters and how to make sure your package version increments with every build.
- [Instructor] In this video,…I'm going to explain how to configure…the TeamCity build server to work with Octopus Deploy.…The first step in setting up a build server…to work with Octopus Deploy…is to decide where you will keep your nougat packages.…Both TeamCity and Octopus Deploy…have built-in nougat servers.…Or you can set up your own independent nougat server.…If you're setting up a production version of Octopus Deploy,…I would recommend a separate nougat server…for performance and maintainability reasons.…
Here's a link to an article by Scott Hanselman,…which has lots of good info…on setting up your own nougat server.…To keep things simple today,…we're going to configure the build process…to use the built-in Octopus Deploy nougat server.…To use the Octopus Deploy nougat server,…we need the URL of the server…and an API key for authentication.…To create the API key,…go to the admin menu and click profile.…Here you can click on the API key section.…This is where you generate a new API key…for communicating with Octopus.…
- What is Octopus Deploy?
- Working with the Octopus server and tentacles
- Using variables to scope configuration items such as roles and targets
- Installing and configuring Octopus Deploy
- Deploying a sample application
- Configuring a build server, adding a project, and creating a release
- Controlling release flow with life cycles and channels