Deploy Release step with prompt for variable

chris.jones's Avatar


09 Feb, 2018 04:56 PM

We're having issues with the new Deploy Release step

We have added a Deploy Release step to a master project.
The child project Requires a prompted variable.
We configured the variable name in the Deploy Release step, bound the value to a variable in the master project

The Release fails at the new step!
"failed with error 'Please provide a value for the following variables: ..."

We can launch the same sub project fine if we use Powershell and pass variable as a param e.g.: Octo.exe deploy-release --project=... --variable=...

  1. Support Staff 1 Posted by Mark Rydstrom on 12 Feb, 2018 12:37 AM

    Mark Rydstrom's Avatar

    Hi Chris,

    Officially we don't support prompted variables in child deployments at this stage. Unofficially it's just the "required" check that fails, so if you are able to set those prompted variables to not be required things should work as expected. In addition I've created an issue in our tracker to get full support for required variables implemented, you can track it here I'd suspect it to be implemented in the next week or two.


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac