Was just going to request this! We have numerous variables that are copied across our projects and we'd love to be able to set them globally. Of course, the option to overwrite at the project level would be desirable.

This seems like such a valuable tool. We have four projects and each project has the same 5 connection strings. This means I have to enter 20 variables per environment but most of the variables are duplicates. It's just a pain. It would be great if I could define some global values higher up the chain.

Global steps too! e.g. Email someone for every deployment to production

This would be fantastic since you could always opt to override it by using project level scopes.

Hi Brian,

It sounds like a very reasonable thing to do. I'm not sure about timelines so I'll update this thread in future when I have more to share.

Thanks again for the input.

Nick

Nicholas,

The set idea sounds great, but is still a bit cumbersome if it requires being set per project. Is there any way to assign a set to an environment and let it trickle down?

Thanks for the feedback; we're introducing a feature called "Library Variable Sets" in version 2 of Octopus Deploy that should cover these needs: projects will be able to include additional sets of shared variables.

You might choose to create a "global" set, a set per environment, per project group or along any other lines you need. (Inclusion won't be automatic, you'll still need to add each set manually to the project.)

https://trello.com/c/3HavDeJl/68-library-variable-sets

I just came here to suggest this. I would also like per-environment scoped variables. The use case for this is simple, I have many services which all need the same connection string per environment.

Variable resolution should first check the project variables and then fall back to the environment variables if one is not set at the project level.

These would be great to set per Environment. :)