The package types supported by Octopus Deploy are:
|Package Type||File Extensions||Repositories||Notes|
|NuGet||.nupkg||Any NuGet repository (including the Built-In repository)|
Currently only NuGet packages will have extra metadata like release notes and description extracted from the package metadata.
|Tar||.tar||Built-In repository only||An archive file primarily used in non Windows environments.|
|Tar + Gzip||.tgz, .tar.gz, .tar.Z||Built-In repository only|
|Tar + Bzip2||.tar.bz, .tar.bz2, .tbz||Built-In repository only|
|Zip||.zip||Built-In repository only||Standard zip file as created through most common zip programs.|
|Docker Image||Docker Registries||Learn about Docker in Octopus Deploy.|
The only required pieces of information Octopus Deploy requires for a package are an ID, Version and Format. Other metadata like release notes or descriptions are optional.
- NuGet packages: NuGet packages support embedding metadata within the contents of the package. We use this metadata to determine the version of the package.
- All other packages: In all other cases we have to parse the file name itself and extract the ID, Version and Format.
The expected package convention is therefore:
So for example the package name for version 2.3 of you project Sample.Web, archived with tar & gzip should be named