Same package deployed multiple times

NOTE: Still using 1.6

We want to deploy multiple copies of the same package to the same environment with different configuration. What is the best way to do that? We want to be able to deploy one project without impacting any other project that uses that package.

The default installation directory is E:\Octopus\Applications\Environment\PACKAGE\Version.

I can use the custom installation directory E:\Octopus\Applications\#{Octopus.Environment.Name}\PROJECT\#{Octopus.Release.Number}\ but that just makes a copy of the original directory. I suspect my custom directories won’t be automatically cleaned up.

Essentially what I want to do is overwrite the $OctopusOriginalPackageDirectoryPath. Is that supported in 1.6? How about in 2.0?

Hi,

If the folder already exists, Tentacle will automatically append a prefix - e.g.,

E:\Octopus\Applications\Environment\PACKAGE\Version
E:\Octopus\Applications\Environment\PACKAGE\Version_1
E:\Octopus\Applications\Environment\PACKAGE\Version_2
E:\Octopus\Applications\Environment\PACKAGE\Version_3

So there should be no problem having multiple projects using the same package, and then using the custom installation directory to have the package copied somewhere else.

(It’s not currently possible to override the extraction directory)

Hope this helps,

Paul