This video explains how to configure the Visual Studio Team Services 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.
- [Narrator] In this video, I'm going to explain…how to configure Visual Studio Team Services' 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 Nuget packages.…Both VSTS and Octopus Deploy have built-in Nuget servers.…Or, if you like, you can set up…your own independent Nuget server.…If you are setting up a production version…of Octopus Deploy,…I would recommend a separate Nuget server.…
Here is a link to an article by Scott Hanselman…which has lots of great info on setting up…your own Nuget server.…To keep things simple,…today we are going to configure the build process…to use the Octopus Deploy Nuget server.…To use the Octopus Deploy Nuget server,…we need the URL of the server,…and an API key for authentication.…To get the URL for the Octopus Nuget server,…click on the Library tab, and look in the Packages section.…Here we can see information about working…with a built-in package server.…
The part that we need…
- 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