Octo is the preferred method when packaging .NET Core applications or applications which generally don't use Visual Studio. Octo can also be used with full .NET framework applications if you require more flexibility than what OctoPack provides. There are other ways to create packages which do not involve our tooling such as using NuGet.exe together with a manifest file (.nuspec file).
Octo is our API command line tool that allows you to interact with your Octopus Deploy server using different commands, one of which is the pack command which can turn any ordinary folder into a NuGet or Zip package - plain and simple. The Octo Command Line page will show you how to get the API command line tool installed and ready to use. All examples on this page however, assume that you are using the portable version of octo installed as a global tool which makes it available through the dotnet cli.
In Octo 3.3.8 we have expanded the functionality of the
pack command to allow creating zip packages in addition to NuGet packages. Learn more.
Octo Basic Usage
At a minimum
octo pack requires an id to be provided:
dotnet octo pack --id="MyPackage"
The above command will generate a package in the current working directory and provide a timestamp based
version number such as
If you want to provide your own version, you can pass the --version parameter in the call to Octo
dotnet octo pack --id="MyPackage" --version="1.0.0"
You can also change the output directory and folder which will be packed with the
--basePath parameters respectively.
dotnet octo pack --id="MyPackage" --version="1.0.0" --basePath="folder/to/pack" --outFolder="destination/folder/path"
Packaging a .NET Core application
The process for packaging a .NET core applications is pretty straightforward and can usually be achieved by publishing the application and then using
octo pack on the resultant output folder for example:
dotnet publish ./OctoWeb.csproj --output ./dist dotnet octo pack ./dist --id="OctoWeb" --version="1.0.0"
Dotnet Core Publish vs Octopack
dotnet publish performs a lot of the heavy lifting that Octopack used to provide and therefore removes much of the need for it in .NET Core.
Please refer to Microsoft's publish and packing documentation for more information.
Packaging a .NET Core Library
If you are using .NET Core for class libraries, we recommend using dotnet pack from Microsoft.
dotnet pack ./SomeLibrary.csproj --output ./dist dotnet octo pack ./dist --id="SomeLibrary" --version="1.0.0"
Packaging a .NET Framework Web application
There are usually some extra steps required to get the resulting application built and deployable. Full framework web applications are a good example of this, where simply building the application will not give you the desired output. We still recommend Octopack for these cases. However, you may be able to achieve this using msbuild parameters such as:
msbuild ./OctoWeb.csproj /p:DeployDefaultTarget=WebPublish /p:DeployOnBuild=true /p:WebPublishMethod=FileSystem /p:SkipInvalidConfigurations=true /p:publishUrl=dist dotnet octo pack ./dist --id="OctoWeb" --version="1.0.0-alpha0001"
Packaging Your Application From a Folder
If you have a build process which places all build outputs into a final destination folder (such as gulp, grunt or webpack), you can package it using octo as well. For example, let's assume you have defined an npm script which runs your build and places all associated content into the
npm run build dotnet octo pack ./dist --id="SomeApplication" --version="1.0.0"
The Octo.exe pack command provides a number of other useful parameters that can be used to customize the way your package gets created, such as including release notes.
You can get help with the pack command parameters by executing the pack command with
C:\> dotnet octo pack --help
The output will explain how to use the command and the different parameters that can be passed to the command:
C:\> dotnet octo help pack Octopus Deploy Command Line Tool, version 3.3.8+Branch.master.Sha.f8a34fc6097785d7d382ddfaa9a7f009f29bc5fb Usage: Octo pack [<options>] Where [<options>] is any of: Basic options: --id=VALUE The ID of the package; e.g. MyCompany.MyApp --format=VALUE Package format. Options are: NuPkg, Zip. Defaults to NuPkg, though we recommend Zip going forward. --version=VALUE [Optional] The version of the package; must be a valid SemVer; defaults to a timestamp-based version --outFolder=VALUE [Optional] The folder into which the generated NUPKG file will be written; defaults to '.' --basePath=VALUE [Optional] The root folder containing files and folders to pack; defaults to '.' --verbose [Optional] List more detailed output. e.g. Which files are being added. NuGet packages: --author=VALUE [Optional, Multiple] Add an author to the package metadata; defaults to the current user --title=VALUE [Optional] The title of the package --description=VALUE [Optional] A description of the package; defaults to a generic description --releaseNotes=VALUE [Optional] Release notes for this version of the package --releaseNotesFile=VALUE [Optional] A file containing release notes for this version of the package Advanced options: --include=VALUE [Optional, Multiple] Add a file pattern to include, relative to the base path e.g. /bin/- *.dll - if none are specified, defaults to ** --overwrite [Optional] Allow an existing package file of the same ID/version to be overwritten