This page describes the Octopus Deploy build event handler settings for deploying a release
A list of one or more environments to deploy to. Each environment should be on a separate line. You can use expressions in this field.
You can choose to one of the following options:
Enter the release version number to deploy. You can use expressions in this field.
Note that all the version numbers in the above fields must be semantically correct according the Semantic Versioning specification.
Force package download
Tick this to force downloading of packages which are already installed
Tick this to override the Octopus Deploy project setting to skip packages with already-installed versions and to force re-deployment.
A list of machine names to target in each deployed environment. If not specified the release will be deployed to all machines in each environment.
This will be displayed as a comment on the deployment on your Octopus Deploy server
Select the event which triggers the Deploy Release action. You can choose one of the following Build Events:
For stage events, select the stage this applies to, or "(all stages)" to trigger the Deploy Release action for all stages
For "On Stage Completed" and "On Build Completed", you can choose to trigger the Deploy Release action when the build is Successful or has Failed.
Uncheck this option to run the Deploy Release action in a separate thread if you don't care about the result eg. whether the action fails or not.
Tick this to fail the build if the Deploy Release action returns an error or failure. This is only available if Wait for Result is ticked.
When this is ticked, Continua will add messages to the build log during execution of the Deploy Release action. Build log messages will only be recorded if Wait for Result is ticked.
The time to wait in minutes for the Deploy Release action to finished.