Octopus Deploy: Variable Scope and Precedence

Since variables can be scoped in many different ways, there needs to be a predictable, deterministic order in which they are resolved. The list below is the priority in which variable scopes take precedence. The top items are higher priority than the bottom ones:

1. The current step/action (most specific).
2. The current machine.
3. Roles applied to the current machine and targeted by the current step.
4. Roles applied to the current machine.
5. The target tenant (if tenant-features are enabled).
6. The target tenant-tag (if tenant-features are enabled).
7. The target environment.
8. The target channel (if channels are enabled).
9. The current deployment process or runbook process.
10. The project.
11. No scope (least specific).

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.