To reduce downtime, Octopus always uploads all packages before installing any of them. For example, given a deployment process that looks like this:
- Run a script
- Deploy package A
- Deploy package B
- Run another script
- Deploy package C
When the deployment runs, Octopus will insert an “Acquire” step to execute as part of the deployment process, before the first step that depends on packages:
- Run a script
- Acquire packages
- Deploy package A
- Deploy package B
- Run another script
- Deploy package C
During the acquire packages stage, Octopus will upload all NuGet packages used in the deployment to all servers. We do this because package uploads can be time consuming, so we want to minimize the downtime between installing packages A and B in this example.
If you have a small window for downtime, you might like to pre-stage your packages. An easy way to do this is to use a manual intervention step. The deployment process would become:
- Acquire packages
- Manual intervention step
- Deploy package A
- Deploy package B
- Run another script
- Deploy package C
Effectively, this will upload all packages, and then pause the deployment until you are ready to proceed. When your downtime window arrives, you can then click Proceed, and have the deployment continue.
When configuring your manual intervention step, take note:
- Under the Package Requirements section, select After package acquisition.
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Sunday, January 1, 2023