The script will execute once per deployment target The script will run on the Octopus Server on behalf of the deployment targets with the web-server role.
Ruby runner to execute script upgrade#
Scope variables to the Step in order to customize variables for this scriptĬalculate some output variables to be used by other steps or run a database upgrade process The script will run once on the Octopus Server
For example, will be the deployment target's nameĪpply server hardening or ensure standard pre-requisites are met on each deployment target The variables scoped to the deployment target will be available to the script. The script will run on each deployment target with either of the web-server or app-server roles See below for some common examples: Target If you choose to run the step on a worker, you will also need to select which worker pool Octopus should use for the step.Ĭhoosing the right combination of Target and Roles enables some really interesting scenarios. Run on a worker on behalf of each deployment target.If you do have workers configured you will see the following options: Run on each deployment target (default).Run on the Octopus Server on behalf of each deployment target.For instance, if you do not have any workers configured you will see the following options: The options will vary based on the infrastructure that's available to you.
When adding a script you choose where the script will run, and in which context the script will run. You can use all of the features we provide for custom scripts, like variables, passing parameters, publishing output variables, and collecting artifacts. You can run scripts contained in a package, or ad-hoc scripts you've saved as part of the step. You can run a script on the Octopus Server, on workers or across the deployment targets in roles. Octopus also allows you to run standalone scripts as part of your deployment process.
0 kommentar(er)
