Before you can deploy an application using Octopus, you will need to bundle all of the executables, DLL's, configuration files, installation scripts, and anything else the application needs to run into a package.
See our supported package types.
On this page:
How you create your packages depends on which package type you wish to create. Octopus generally treats all packages the same, so choose the tooling and package type that is easiest for you to create. For example:
- ASP.NET apps (.NET Framework): use OctoPack
- Windows Services (.NET Framework): use OctoPack
- .NET Core apps: use
- Working with TeamCity: use our extension,
octo.exe packor even the built in tools for TeamCity
- Working with VSTS: use our extension and/or
- Just want to package up a folder as-is: use
octo.exe packor just zip it up!
As long as you can create one of our supported packages, you can deploy your application with Octopus Deploy!
Packages are kept in package repositories (or feeds). A repository can be as simple as a file share, or it could be a dedicated server. For more information, see the section on choosing a package repository.
What's in a package?
Octopus expects your package to contain all of the files needed to run the application when it is deployed (along with any scripts needed for deployment, and any configuration transformation files, etc).
An ASP.NET MVC application, packaged using NuGet for example, would look like this:
While a Windows Service application might look like this:
Note that in both examples:
- Only binaries and files needed at runtime are included - C# source code files, for example, are not in the package
- The binaries aren't just for the current application - they also include any other assemblies needed for the application to run