"Deploy a Release" step and Environments

[RobertEarnshaw]

Consider that you have two Projects, Project A and B

Project A has a lifecycle that has Production in it, with no Servers (its a meta project)
Project B has a lifecycle that has Production with Two servers, Server A and Server B

Project A kicks off Project B, is there a way to tell Project B which of the two servers to deploy to?

[Kenneth_Bates]

Hi Robert,

Thanks for getting in touch! Unfortunately there’s no way I’m aware of to control which server the child project is deployed to based on input from the parent project. While you can pass variables to the child project in the Deploy Release step, a run condition on the package step in the child project wouldn’t work as run conditions are evaluated for the whole step. Either the variable condition evaluates to true and runs the step, or it evaluates to false and doesn’t run at all.

You could control this by scoping the steps in the child project to a unique role which is only assigned to one of the servers, but it wouldn’t allow you to easily decide which server to deploy the child project to at deployment time.

Would you be willing to expand a bit on your scenario? Perhaps there could be a more out of the box solution based on your requirements.

I look forward to hearing back!

Best regards,

Kenny