With Octopus Deploy you can deploy software to Windows servers, Linux servers, Microsoft Azure, AWS, an offline package drop, cloud regions, or Kubernetes. These machines and services are your deployment targets, and because software is typically deployed to more than one machine (or deployment target) Octopus organizes your deployment targets into groups called environments. Typical environments are Development, Test, and Production, you can also assign target roles to your deployment targets to further refine which deployment targets your software is deployment to. You can use workers to perform tasks that don't need to be performed on a deployment target or on the Octopus Server.
You can manage your environments, deployment targets, and workers from the Infrastructure tab of the Octopus Web Portal.
You need to set up accounts for certain deployment targets before you can use them:
Adding Deployment Targets to Environments
Deployment targets are added to environments in different ways, depending on the type of target and how they will communicate with the Octopus Deploy Server.
- Listening and Polling Windows Tentacles
- SSH Connection
- Offline Package Drop
- Azure Web App
- Azure Cloud Service
- Azure Service Fabric Cluster
- Kubernetes (Currently in beta)
- Cloud Regions
Octopus comes with a built-in worker that can run scripts and perform tasks that don't run on deployment targets. You can configure external workers and pools of workers to move these tasks off the Octopus Server for better performance and increased security.
In This Section
The following topics are explained further in this section: