Variables not always passed to environments during deployment

Legacy Uncategorised
1

I have a variable table set up as follows:

Name Environment Machine Step Value
DatabaseServer env2 Database (All) qadbs01\qa_ft_q3
DatabaseServer env1 Database (All) qadbs01\qa_ft_01
PortalDatabase (All) Database (All) Portal

When I do a deployment to env1, I get all variables as I expect them. however when I do a deployment to env2 I do not get the variables passed to my Powershell scripts as I would expect.

Log output from Env1:
2011-09-22 21:14:37 DEBUG The following variables are available:
2011-09-22 21:14:37 DEBUG - [portaldatabase] = 'Portal’
2011-09-22 21:14:37 DEBUG - [skipinstallutil] = '.+'
2011-09-22 21:14:37 DEBUG - [databaseserver] = 'qadbs01\qa_ft_01’
2011-09-22 21:14:37 DEBUG - [OctopusEnvironmentName] = 'env1’
2011-09-22 21:14:37 DEBUG - [PackageRoot] = ‘C:\Octopus\Tentacle\Applications\Portal-DB.3.2.8710.62’

Log output from Env2:
2011-09-22 21:13:36 DEBUG The following variables are available:
2011-09-22 21:13:36 DEBUG - [skipinstallutil] = '.+'
2011-09-22 21:13:36 DEBUG - [OctopusEnvironmentName] = 'Connie Esguerra’
2011-09-22 21:13:36 DEBUG - [PackageRoot] = ‘C:\Octopus\Tentacle\Applications\OPS-Portal-DB.3.2.8710.62’

Is there a work around for this issue? Thanks, Karl

2

Hi Carl,

It looks like your ‘env2’ variable is pointing to the same machine (which I’m guessing belongs to env1). Is that the case?

Paul

3

My apologies for spelling your name wrong Karl!

4

That is correct, both environments are on the same physical machine.

Also, I am using version 0.8.391.2008 (both Tentacle & Octopus)

5

Hi Karl,

In Octopus a Tentacle belongs to one (and only one) environment. Your env2 rule is being ignored because the machine belongs to a different environment. Octopus should probably show an error when this happens.

The way to approach this would be to create two “machines” in Octopus, one in each environment, with different names. These would actually point to the same Tentacle, but they would be treated as two logical machines.

Env1
     Database1 -> Points to Database
Env2
      Database2 -> Points to Database

Paul

6

Hey Paul,

Thanks this helped. Turned out I did have my environment set up in this way. The problem turned out to be that both environments were pointing to the database machine for Env1. (actually all the env2 variables were pointing to the env1 machines)

What made matters worse is that they both had the same name so it wasnt immediately obvious until i hit the drop down menu again.

Thanks again!

Karl