Supported Formats

Last updated

Octopus Deploy supports several package types that can be used when packaging your applications and will continue to add more in the future.

Octopus uses the file extension to determine the correct extraction algorithm to use, so it is important that your package has the correct extension for the package format.

Learn more about creating packages.

Package Type File Extensions 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 and Octopus Deploy.
JAR WAR EAR RAR .jar, .war, .ear, .rar Built-In repository (and Maven Feeds from 4.1) Learn about Maven Feeds.

Learn about package IDs, versioning, creating packages, and package repositories.

Pre-Release packages and Multipart file extensions

If you're planning to use a multi-part file extension (e.g. .tar.gz) with a pre-release naming convention (MyApp.1.0.0-beta.tar.gz) and use the Run on Server steps option, this will result in an error message of Unsupported file extension .gz. This is because the .tar forms part of pre-release tag and not part of the file extension.

The error only occurs on Run on Server steps and deployments execute on as expected on Tentacles.