Last night we updated to Octopus 3.4.5 from 3.3.19.
We just discovered that all our variables that have a scope for Environment doesn’t show in the “drop down” list with variables you can use.
We have tested to use different scopes and realised that this only occurs when we use Environment as a scope.
This issue has been confirmed in numerous projects with different life cycles aswell as on our test environment where we do our upgrade tests before we upgrade our production installation of Octopus.
The variables CAN be used if you type in the actuall name of them, so there is a work around, a harsh one though
Thanks in advance
Thanks for getting in touch and reporting this problem! This looks like it’s an issue we’ve logged already: https://github.com/OctopusDeploy/Issues/issues/2684
Let me know if that seems like the case, or not.
Hope that helps!
Yeah its the same issue!
Thanks for getting back to me
Operations | System Engineer
This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.