Can you serialize a deployment step?

Automated deployment for web applications and databases

Can you serialize a deployment step?

Postby isme » Mon Jan 13, 2014 3:57 pm

Hey RG,

When you assign multiple targets to a deployment step, RGDM deploys to each target in parallel.

We have a step that does not run safely in parallel. Deployments fail unpredictably because of deadlocks.

We want to run the step strictly against one target at a time to avoid the deadlocks.

Octopus Deploy supports this through the special OctopusMaxParallelism variable.

Paul Stovell explains:

you can set a special variable called OctopusMaxParallelism to a value of, say, 5. This way the step will only be executed on 5 machines at any given time. If one machine finishes, then the next will start, and so on, with only 5 ever running at once.


Does RGDM have something similar? If it existed, we would try setting it to 1.

If you don't support this yet, do you have a workaround instead?
Iain Elder, Skyscanner
isme
 
Posts: 83
Joined: Tue Jun 12, 2012 1:49 pm
Location: Edinburgh

Postby james.billings » Mon Jan 13, 2014 6:21 pm

Hi,
That doesn't look to be something we currently support I'm afraid. Could you add it as a feature request over on our Uservoice page ?
james.billings
 
Posts: 1120
Joined: Wed Jun 16, 2010 11:10 am
Location: Red Gate

Postby isme » Thu Jan 16, 2014 12:00 pm

I defined "RedGateMaxParallelism = 1" for the critical step, but it had no effect. :-)

Added my request to implement this on Uservoice.

Thanks, James!
Iain Elder, Skyscanner
isme
 
Posts: 83
Joined: Tue Jun 12, 2012 1:49 pm
Location: Edinburgh


Return to Deployment Manager

Who is online

Users browsing this forum: No registered users and 0 guests