Multi-Tenant Install

Legacy Uncategorised
1

Hey Paul,

I have an issue where I have a server which hosts both Dev and Pre-Prod currently. I specify OctopusPackageDirectoryPath on Dev, and expect that Pre-Prod will still be deployed as it will end up in a different spot.

I think Octopus needs to support this multi-tenant scenario, i.e transforms etc are all run after the files are copied to $OctopusPackageDirectoryPath or some other method.

Cheers,
Jake

2

Hi Jake,

Last night I actually just finished the work on a feature to allow this, which will be in the next release.

Previously, Tentacle extracted to:

C:\Octopus\Applications\Acme.Web.1.0.0

From now on, it will extract to:

C:\Octopus\Applications<Environment><Package><Version>

So for example:

C:\Octopus\Applications\Pre-Production\Acme.Web\1.0.0

That should alleviate this problem going forward.

I am curious about this though:

i.e transforms etc are all run after the files are copied to $OctopusPackageDirectoryPath or some other method

This should already work. Can you possibly post the output log?

Paul

3

That should be fine, the second issue/question was more I didn’t know what it did. After I posted I verified force works fine.

Sent from my Windows Phone

From: Paul Stovell
Sent: 18/05/2012 5:13 PM
To: jake@ginnivan.net
Subject: Re: Multi-Tenant Install [Problems]

4

Cool. I’ve changed the behavior of force as well. Previously if you had:

C:\Octopus\Applications\Acme.Web.1.0.0

Force would wipe the directory before re-installing. But that fails if the processes are locked.

Instead it will now just create this:

C:\Octopus\Applications\Pre-Production\Acme.Web\1.0.0_1

So if you do a ‘forced’ deployment of the same package 3 times, you’ll get:

C:\Octopus\Applications\Pre-Production\Acme.Web\1.0.0_1
C:\Octopus\Applications\Pre-Production\Acme.Web\1.0.0_2
C:\Octopus\Applications\Pre-Production\Acme.Web\1.0.0_3

Later I’ll add the ability for Tentacle to automatically clean up the obsolete folders.

Paul