Deployment plans and application level variables

[Guest]

Hi there,

I have a deployment plan that pushes an installation out to a server...based on a property of the particular application, I'd like to execute different commands on the server

For example, if an application variable called "apptype" = 1, I want to stop some services on the server first...otherwise, I don't.

Is this possible with variables?

Thanks,

Chris

Product: BuildMaster
Version: 4.8.6

[Guest]

Sure, just use the Variable predicate on the action group that contains the commands you want to run. If you have a bunch of different commands that will be shared across multiple applications, just make a new Global Deployment Plan that has all the logic for which commands to run using multiple groups & predicates, then use the "Execute Deployment Plan" action for whatever applications you want to run the commands.

[Guest]

Hi Tod,

Thanks for your answer! Here's what's throwing me.

If I set up an "application level variable" called "apptype" on each of the applications, will the deployment action groups be able to see that application level variable in their predicate? The action group would need that to decide whether or not to execute, right? Or should the variable be defined somewhere else at a different level?

I have a global deployment plan that wants to run separate action groups (based on this apptype variable):

if (apptype = service)

• stop some services
• run an installer
• start some servers
  end
  if (apptype = tool)
• copy the installer to the system
  end
  if (apptype = web component)
• stop IIS
• run an installer
• start IIS
  end

[Guest]

Variable values are "cascaded" by the execution engine at runtime. So, yes; if you define it any level (server, environment, deployable, etc)., it will resolve the most specific variable definition (e.g. a "build" variable overrides a "global" variable, etc).