One deployment, all branches?

Bryan_K

We have created a "super workflow" which I posted about earlier in the workflow forum. The purpose of this super workflow is to be a generic flow that is called from all branches and users but which uses a different list of approvers depending on which branch it is called from. We do this by retrieving approver information from an Oracle DB, which stores the appropriate info for each branch.

We would now like to write a generic deployment that will also store remote destination location in the DB, and deploy the content from the branch the user is currently in, to the destination location retrieved from the DB.

What is the best way to do this? Is there a way to insert a destination location variable in an xml deployment file?

I am also going to post this question in the workflow forum.

Bryan

tvaughan

Hi Bryan,

I've implemented the kind of deployment you're talking about. You need to make liberal use of the variables allowed within OpenDeploy 5.x configuration files.

One of my typical deployment config files looks something like this:

< ?xml version="1.0" encoding="UTF-8"?>

< deploymentConfiguration   nodeSetFile="/opt/od5/opendeploy/OpenDeployNG/etc/odn
odes.xml" >

  < localNode  host="$hostname^" />

  < replicationFarmSet>
      < replicationFarm name="FreddieMac Staging" >
          < nodeRef useNode="hq2unx135" />
          < nodeRef useNode="hq2unx137" />
      < /replicationFarm>
  < /replicationFarmSet>

  < definition  name="TS2FMstaging">
      < source>
          < sourceFilesystem  area="$source_area"
                             filelist="$filelist" >
              < pathSpecification>
                  < path name="." />
              < /pathSpecification>
          < /sourceFilesystem>
      < /source>
      < target useReplicationFarm="FreddieMac Staging" >
          < comparisonRules  dateDifferent="yes" />
          < permissionRules  directory="0775"
                            file="0775"
                            user="iwfmmgr"
                            group="nogroup">
          < /permissionRules>
          < targetFilesystem area="$target_area" />
      < /target>

  < /definition>

  < deployment transactional="yes"  >
      < execDeploymentTask  useDefinition="TS2FMstaging" />
  < /deployment>

  < logRules   maxBytes="32Mb"
              level    ="VERBOSE"
              />

< /deploymentConfiguration>

The value for $source_area, $filelist, and $target_area are computed by a response CGI to a custom menu item (File-->OpenDeploy). Based on who the user is, where they are, and what role they have, I'll allow them to utilize zero or more different deployment configurations (with the above being 1 such possibility). The CGI fills in the variable names and creates the iwodstart command to be executed.

Tom