transactional and non-transactional deployment

LooseKannon

Hi There,
I was hoping somebody could guide me on a problem i am facing. Basically the client has 5 servers in total that it needs to deploy to. It wants to do transactional deployment on 4 of them and non-transactional on 1 of them.

The client wants to make sure that if the 1 server that is non-transactional fails, it doesnt rollback the other four. The only time the 4 servers should rollback is when one of them fails.

How can i do this in one shot. Somebody had suggested using a dnr script to call another deployment. E.g. within a non-transactional deployment, call a dnr script that will run another deployment for the transactional. But i am thinking that if the non-transactional deployment fails then the script will not get executed?

If i do it the other way, e.g. within a transactional deployment call a script that will run a non-transactional deployment,. ...then it wont get to the script part if one of the four servers fail to deploy.

Can anybody suggest a way to go about doing this.

We are using OpenDeploy 6.1.1 with TeamSite 6.7.1. Any help is much appreciated.

ISCBorisB

But i am thinking that if the non-transactional deployment fails then the script will not get executed?

That's actually configurable. <dnrDeployment> Tag has an attribute state="[success | failure | always]". Default is "always" so
unless you set it otherwise your DNR will run on Deployment Failure as well.

That said, the best way to mix transactional and non-transactional Deployments is IMO not to mix them at all. In any subsequent automation,
deployment return code processing, scheduling and whatnot two separate Deployments will be much easier to develop, debug, maintain and
Administer. You can always combine them within simple code/script/batch if that's what you really want.