Disabling a step removes all variables scoped to it


I’m working with Octopus version 3.8.2. As mentioned in the subject: after disabling a step - all the variables scoped to that step are gone. This applies to project variables, haven’t tested it with variable sets. This makes a step disabling feature a bit dangerous - we’ve just lost some variables and needed to recreate them. Are there any ways of going around this? I mean besides scoping the steps to a dummy environment instead of disabling them.


Hi Krzysztof,

Thanks for getting in touch! Unfortunately you’ve hit a bug in Octopus. The good news is that it is already fixed in Octopus ‘3.8.4’. Please upgrade your server to the latest version and the problem should be fixed.

Please, let me know how you go.