Restarting servers is typically the responsibility of the Operations team as restarting a machine requires elevated permissions. With a runbook, you can give developers the ability to restart a machine whenever they need. The auditing feature of Octopus Deploy records the identity of the person who initiated the run of the runbook so you can always see who did what and when.
Unlike most other runbooks, this type of operation needs to run on a worker machine instead of the machine that needs to be restarted. This is to ensure communication to the Tentacle isn’t interrupted, as it would be when the machine restarts, which would result in a failed run of the runbook.
Create the runbook
- To create a runbook, navigate to Project ➜ Operations ➜ Runbooks ➜ Add Runbook.
- Give the runbook a name and click SAVE.
- Click DEFINE YOUR RUNBOOK PROCESS, then click ADD STEP.
- Add a Run a script step
- Change the Execution Location to
Run on a worker on behalf of each deployment target - Select the role from the
On Targets in Rolesdrop-down list. - Select the radio button that corresponds with the language you’re using and enter the inline source code:
PowerShell
Invoke-Command -ScriptBlock { Restart-Computer } -ComputerName #{Octopus.Machine.Name}
Bash
ssh #{Octopus.Machine.Name} sudo reboot
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Sunday, January 1, 2023