Now that you've installed Octopus and Tentacle, and you've created your environments and a project, and your applications have been packaged for deployment, it's time to look at deploying applications with Octopus Deploy.
On this page:
Each project has a deployment process, which can be found on the Process tab of the project in the Octopus web portal. The deployment process is like a recipe. It defines the set of instructions that will be run repeatably each time the project is deployed. The deployment process can have one or more steps, and the steps can be ordered using the Reorder steps link.
Steps can be added to the deployment process using the Add step button. There are many different types of steps supported by Octopus and we are adding more specific steps all the time. For more information, see the add step section.
Common step properties
All steps have a name, which is used to identify the step.
Steps can also have conditions. You can restrict a step so that it only runs when deploying to specific environments (e.g., an Email step that only runs on production deployments).
If you have created some channels, you can also specify whether a step runs only when deploying a release through specific channels (e.g., a Script step that only runs for deployments through certain channels to configure extra telemetry). This will only appear if you have created one or more non-default channels.
You can also specify whether a step runs only when previous steps are successful (default), when a previous step fails, or always.
In this section
- Adding steps
- Deploying packages
- Configuration files
- Custom Installation Directory
- IIS Websites and Application Pools
- Windows Services
- Custom scripts
- Delta compression for package transfers
- Email notifications
- Step Templates
- SQL Server databases
- Guided failures
- Manual intervention and approvals
- Scheduled Deployments
- Automatic Release Creation
- Automatic Deployment Triggers
- Run steps in parallel
- Deploying to Azure
- Substitute Variables in Files
- Blocking Deployments
- Docker Containers
- Azure deployments
- Cloud Services
- Creating an Azure Account
- Resource Groups
- Running Azure PowerShell
- Varying Azure Subscription by Environment
- Web Apps
- Deploying ASP.NET Core Web Applications
- Multi-tenant deployments
- Multi-tenant deployment guide
- Multi-tenant deployments FAQ
- Other scenarios for multi-tenant deployments
- Troubleshooting multi-tenant deployments
- Multi-tenant deployments prior to Octopus 3.4
- Node on *Nix deployments
- User Role & Teams Configurations
- Use the Team Foundation Build Custom Task
- Elastic and Transient Environments
- Server Extensibility
- Octopus HA
- Coordinating Multiple Projects
- Deploying Java applications