This documentation is for Octopus Deploy Version 2018.9. View other versions

Packaging Applications

Last updated

Deploying software with Octopus Deploy involves defining your deployment process with predictable and repeatable steps. Often, part of the deployment process will involve deploying a package. This sections explains how to package your applications for deployment with Octopus.

Before you can deploy your software you need to:

  1. Decide which format to use to package your software.
  2. Give your package a package ID.
  3. Choose and apply a versioning scheme for your software.
  4. Create the package with all the files your software needs to run.
  5. Host the package in a package repository, for instance, the built-in Octopus feed.

The combination of a package format, package ID, and version number makes deploying your software across different environments repeatable, reliable, and predictable. This means that once the deployment process has been defined, your software can be deployed again and again. Octopus makes it easy to track which software has been deployed to which environments and isolate specific changes within the software.

Example Package

One of the simplest examples of a package that is deployable by Octopus looks like this:

In this example we've used zip as the format, hello-world as the package ID, and 1.0.0 represents the version number for this version of the package. Read on to learn more about these concepts and how to implement them with Octopus.

In This Section

The following topics are explained further in this section: