Is it possible to order the tenants in a deployment

functionality
(S Honig) #1

We have one server for all test environments which we use for all our tenants. If we do a deployment for test all these deployments starts paralel so it will take a long time for all deployments to finish.
Is it possible to do this in a specific order (order of tenant) ?

(Daniel Fischer) #3

Hi @s.honig,

Thanks for getting in touch! This is not currently possible in Octopus. Each Tenanted deployment is regarded as an individual deployment and it’s assumed the ordering should not have any impact on the deployments.

We are curious about how the ordering of the Tenanted deployments is impacting you here. Would you be able to provide some details about the impact of these un-ordered Tenanted deployments?

Looking forward to hearing from you.

Best regards,
Daniel

(S Honig) #4

Hi Daniel,

Because all deployments are started paralel on the same server the creating of backups and the copying of packages makes it very slow. If we deploy a single tenant it will cost about 2 minutes. If we deploy all tenants it will cost about 40 minutes (14 tenants) and most of the time the tenants are unavailable or unusable because of the overall server performance while deploying.

Best regards,
Sven

(Daniel Fischer) #5

Hi Sven,

Thanks for getting back. As each Tenant selected to be deployed is executed as a separate task, the global task cap in Octopus can be used to control how many Tenants are deployed to in parallel. The default Task Cap is set to 5 tasks running in Parallel, however this can be adjusted. By default Octopus should not be deploying more than 5 Tenants at a time to your target, unless this Task Cap value has been changed.

You are able to reduce it further if you would like to deploy fewer Tenants in Parallel. This task cap is global though and will affect all tasks on your Octopus server.

Let me know if you have any further questions here.

Best regards,
Daniel