When a deploy a release step is used the sub project being released cannot use a deploy a release step itself as the version selection does not pass through to the parent.
Thank you for reaching out to us with your query.
It should be possible for the “Deploy a Release” step to be nested an unlimited number of times and it should work the same at each level, so we’ll need to investigate this further.
Can you please advise how you are capturing the output at each level? It’d be great if you could provide a copy of your deployment process JSON as an attachment too (please ensure anything sensitive is redacted if you choose to do so).
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.