Prompted Variables to save value per Release.
This would allow Repeatable Release from Dev to QA to Prod.
You would ask for value in begging of life cycle just like now,
but for QA and Prod it would Retain that value entered in Dev as preset.
thank you
Boris Gligich
shared this idea
-
Brian
commented
I am really surprised this functionality doesn't exist. It seems so fundamental. Please add this feature.
Here is another similar issue:
https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6319014-associate-variables-with-a-release-when-creating-o -
Keith D
commented
As of part of this, it would be useful to be able to see the prompted values which will be or were used during a deployment. At the moment, the only way to do this is to output from a script, but that doesn't allow you to view prompted variables that were entered for scheduled deployments which haven't run yet
-
B Au
commented
As part of the change, it would help to have the ability to switch the feature on/off.
-
Matt Miner
commented
Agreed. We have version strings that we just need to set per release. We've had to resort to uploading empty packages just to get access to this value.
-
Anonymous
commented
This is useful as some variables are specific to a release (rather than a deployment) and can't easily be established from code. My example would be the EF migration to target. The prompt is a great feature, as it allow capture of that information at the time it is needed - but its annoying that it is only available at deployment - meaning we have to document the values for whoever does the deploy rather than having them saved to the release