Running sub deployments

blacke

Does anyone have a suggestion as to what would be the best way to run sub-deployments? What I mean by that is I have a bunch of individual deployments that need to be run individually most of the time, but occasionally I'd like to run them all as a group from one deployment that would include all the others as sub-deployments.

The only way I can think to do this is with dnr scripts in the 'parent' od deployment script that would kick off a bunch of separate deployments. (I have to run a deployment because this is part of a workflow).

The only other thing I could think of was somehow using multi-tiered deployments back to the base server, but that doesn't seem possible or promising.

Any suggestions would be helpful. Thanks

Adam Stoller

Does anyone have a suggestion as to what would be the best way to run sub-deployments? What I mean by that is I have a bunch of individual deployments that need to be run individually most of the time, but occasionally I'd like to run them all as a group from one deployment that would include all the others as sub-deployments. The only way I can think to do this is with dnr scripts in the 'parent' od deployment script that would kick off a bunch of separate deployments. (I have to run a deployment because this is part of a workflow). The only other thing I could think of was somehow using multi-tiered deployments back to the base server, but that doesn't seem possible or promising. Any suggestions would be helpful. Thanks

Since I believe you're talking about deployments from server-A to server-B I don't believe multi-tier is an option (that's used for deployments from server-A to server-B, followed by deployments from server-B to server-C, ... where server-B is a second Base Server) - though I suppose you could write a wrapper deployment that does a loop-back, ...

I think the DNR approach is probably reasonable - although if the logic for determining when you need to run all the deployments can be programmed, you could just write a wrapper script to issue the N deployments - either sequentially or concurrently -- the downside being that the "set" of deployments cannot be made transactional in this manner. If you don't care about having everything be within a single (or even multiple) transaction(s) [for rollback] - then either the DNR or wrapper-script approach seems to be sufficient as far as I can tell.

A possible feature request that you might feel like logging with IWOV Support would be for some way to "include" deployment configuration files within other deployment configuration files and to be able to use some form of "conditional logic" within the deployment configuration file to determine if/when to do so ... but at this point it seems like a one-off kind of request and thus there's not much rationale for trying to complicate the product to deal with it.