You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't prevent deploy release steps being child steps. At the moment this crashes because the step doesn't implement ITargetActionHandler. That would be easy enough to do, but not in a meaningful way. That implies you accept a Machine, and Deploy Release can't do anything with a machine or role, it can only deploy a release. It doesn't make sense to say "Deploy this release to this role" as all the role information is down on the project you are deploying.
We'll block users making them child steps instead.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.
lockbot
locked as resolved and limited conversation to collaborators
Nov 23, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bugThis issue represents a verified problem we are committed to solving
We don't prevent deploy release steps being child steps. At the moment this crashes because the step doesn't implement
ITargetActionHandler
. That would be easy enough to do, but not in a meaningful way. That implies you accept a Machine, and Deploy Release can't do anything with a machine or role, it can only deploy a release. It doesn't make sense to say "Deploy this release to this role" as all the role information is down on the project you are deploying.We'll block users making them child steps instead.
The text was updated successfully, but these errors were encountered: