Transactional to a single server/path

OpenDeploy 6.2.0.0 Patch 1

The Requirement:
We need to perform two deployments to the same path on a single receiver. The first deployment needs to be directory comparison and the second a file list. Plus they need to be transactional ... if either fails, they both roll back.

The Issue:
The transactional setting seems to make each of the deployments wait till they've locked the path on the receiver before they start. So our first deployment locks the path and then waits for the second deployment. The second deployment keeps trying to lock the path, but can't (it's already locked by the first deployment). After 30 minutes the deployment dies.

To me our requirement seems pretty simple ... can OD be configured to handle this?

[HTML]

[/HTML]

Find more posts tagged with

Comments

Pawan

If it is feasible to run a DNR script on your target receiver, then you can redirect one of your deployments to a temp path on the receiver and after both the deployments are successful, run the DNR script to copy the files to the appropriate location.

Assumption: Copy Operation is successful always.

Adam Stoller

OpenDeploy 6.2.0.0 Patch 1

The Requirement:
We need to perform two deployments to the same path on a single receiver. The first deployment needs to be directory comparison and the second a file list. Plus they need to be transactional ... if either fails, they both roll back.
[...]

I don't think this is "simple" - also - just to make sure - you're trying to deploy files from one TS server to another TS server - yes? If so, why are you accessing the source through C: and the target through Y: ?

Assuming that you are deploying from TS-1 to TS-2 - you could probably wrap the deployment process in a script that did something like the following:

to be doing.