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

Deployment Targets

Last updated

Now that you have packaged your application, you need something to deploy it to. The destination might be a Windows server, or an Azure web application, or a Linux server running SSH. In Octopus, each of these destinations are called Deployment Targets.

Before you can add deployments targets, you need to set up Environments.

Learn about Environments.

Deployment targets are added to an environment from the Environments page.

A deployment target can be one of the following types:

Listening Tentacle 

A Listening Tentacle is a machine with the Tentacle service installed in listening mode.

Polling Tentacle 

A Polling Tentacle is a machine with Tentacle service installed in polling mode.

Offline Package Drop 

An Offline Package Drop target is designed to allow deploying to a machine which the Octopus Deploy server cannot communicate with; for example, due to security policy or network topology.

SSH Connection 

Currently, the Tentacle service can only be installed servers running Microsoft Windows. An SSH Connection target allows deployment to Linux machines.

Cloud Region

Cloud Region is a way to model multi-region deployments as a way to replace the deprecated Azure Web App and Azure Cloud Service targets.

Azure Web App 

Azure Cloud Service deployment targets have been deprecated in Octopus 3.1. Don't worry - you can migrate your Azure Targets to use the equivalent Azure Steps by following this guide.

Azure Cloud Service 

Azure Web App deployment targets have been deprecated in Octopus 3.1. Don't worry - you can migrate your Azure Targets to use the equivalent Azure Steps by following this guide.

In This Section

The rest of this section covers these topics in some more detail, and explains how to implement them.