This page is for Octopus Deploy 3.0 and newer versions. You can view this page for Octopus 2.0

Skip to end of metadata
Go to start of metadata

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.

Isn't Octopus Deploy all about NuGet?

Icon

Originally, Octopus Deploy supported only NuGet packages but that is no longer the case. In Octopus 3.3 we added support for zip packages, and in Octopus 3.5 we added support for Docker images. We will be continuing to support other packaging concepts as they become relevant to the deployment ecosystem.

While some of our documentation may still refer to NuGet packages specifically, all packages are generally treated the same.

On this page:

Creating packages

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:

As long as you can create one of our supported packages, you can deploy your application with Octopus Deploy!

Choosing the best versioning scheme

Icon

When creating your packages you will need to choose a versioning scheme that is supported by Octopus Deploy and suits your needs. Learn about versioning in Octopus Deploy.

Hosting packages

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
  • No labels