nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multiple Deploy

chriskmt

Hello,
I have recently inherited the workflow developer position. I have had no training but I am trying to bump my way through this. One of the most recent requests was to have a deploy happen for two targets. Right now, there are radio buttons to choose which server you would like. There was a workflow that we used to use on an older install (cgi file), but when I open it, it looks compiled, I can't edit it or borrow code from it.

So I am hoping someone can point me in the right direction, I assume there needs to be some kind of call back for when the first deploy clears so the second one can start, but that is about it. If someone can offer an outline, the workflow we use now submits to staging then deploys to the target.

I appreciate it!

Find more posts tagged with

Comments

karel

first, read the WFM guide.

Create a new workflow with the WFM, add a submit task & 2 deploytasks, each with a different target.

Or modify your deployment configuration to deploy to 2 target nodes.

chriskmt

I have been looking at the workflow modeler, I was hoping to use the existing workflow and add some type of if statement that looks to see if the both servers are selected (checkboxes rather than radio). This is only because I know the submit and deploy WF is very customized. There are actually four servers involved, two IIS boxes and two java boxes. Each 'target' checks the file list for images, css and js and sends to IIS, otherwise it gets sent to the java servers. Do you think this can be done simply with the WFM?

I also was looking at the successor set, could this be used as well?


<externaltask name="Deployment"
     owner = "__INSERT__($jobOwner);"
     description="Deployment To Webserver" >
 <areavpath v = "__INSERT__($vpath);"/>
 <successors>           
    <successorset description = "Successful deployment to Webserver">
   <succ v = "End Task"/>
  </successorset>            
  <successorset description="Deployment Error">
   <succ v="Fix Deployment Problem"/>
  </successorset>
 </successors>        
 <command v="__INSERT__($deploy_cmd); __TAG__('iw_deploy_to');"/>
</externaltask>

If it would be something as simple as adding another successor set, that would be nice. I know you have no idea what I am exactly working with, but if theoretically I can just tell the deploy to run again if there is more than one checkbox selected…

nipper

Ignore the WFM reference, you use WFT. Your requirements are not well laid out.

You say you have 2 radio buttons, what are they ? How does that play into the 2 deployments ? Do you want 2 deployments all the time, no matter what ? Then add a second deploy task (which uses a different successorset).

But I do not think what you want is as simple as that.

chriskmt

Thanks for sticking with me.

We have a dev box and qa box (testing area). I have been asked to set up the workflow so that files can be sent to the dev and/or qa box. Right now there are radio buttons that go to one or the other, they don't want to have to re-submit the same files, but if they wanted to, they could submit to only one or the other.

So i have checkboxes now, and they work as long as they aren't both checked. I assumed I could check to see if the $deployTo value was an array, if it was send it once to each box ("dev" -- $deployTo[0] then "qa" -- $deployTo[1]), if not send it to the value of $deployTo which could be "dev" or "qa".

this is from the WFT :


iw_deploy_to => [ html => 
   <INPUT TYPE='checkbox' NAME='DeployTo' id='dev' VALUE='dev'><label for='dev'> <strong>Development</strong></label>
      <INPUT TYPE='checkbox' NAME='DeployTo' id='qa' VALUE='qa'><label for='qa'> <strong>Test</strong></label>    <br /><br />
      <a href=\"javascript&colon;;\" id=\"enProd\" style=\"visibility:hidden;\">Production Deploy?</a><br />
      <INPUT TYPE='checkbox' NAME='DeployTo' VALUE='prodOne' disabled=\"disabled\" id='prodOne' > Production 1
      <INPUT TYPE='checkbox' NAME='DeployTo' VALUE='prodTwo' disabled=\"disabled\" id='prodTwo' > Production 2<br /><br />
      ",
     is_required => 'true',
      label => "Deploy To",],

   "Files" => [ html => $filesHtml,
     is_required => 'false',
     label       => 'Selected Files',],

Then the ipl file has this code. It looks like it is half way there with the array and for each except the condition in the if says equal, wouldn't that be 'contains' or something:


    # LOAD DESTINATION SERVERS INTO AN ARRAY
    my $serv_ctr = 0;
    if ($deployTo eq "dev") {
       $servers[$serv_ctr] = "dev";
       $serv_ctr++;
    }
    if ($deployTo eq "qa") {
       $servers[$serv_ctr] = "qa";
       $serv_ctr++;
    }
    if ($deployTo eq "prodOne") {
       $servers[$serv_ctr] = "java1_Prod";
       $serv_ctr++;
    }
    if ($deployTo eq "prodTwo") {
       $servers[$serv_ctr] = "java2_Prod";
       $serv_ctr++;
    }
    my ($i, $local, $remote_dir);

    for ($i=0; $i<$serv_ctr; $i++) {
       if ($servers[$i] ne "0") {

            $DEPLOY_TO = $servers[$i];     
  my $DEPLOY_SCRIPT = "custom_deploy_flist";
   &debug("IMAGE PATH is $IMAGE_PATH");
  &debug("$DEPLOY_TO ");


               ##### bunch of code that checks file type and path (code removed)#######


open(FILE,">F:\\logFile123");
     my $deploy_cmd = join(" ",
                               "$odhome/bin/iwodcmd start",
                               "$DEPLOY_SCRIPT",
                               "-k \"lnode=$lnode\"",
                               "-k \"flist=$deploy_filelist\"",
                               "-k \"targetNode=$DEPLOY_TO\"",
                               "-k \"localDir=$local\"",
                               "-k \"remoteDir=$remote_dir\"");


close FILE;

   &debug("$deploy_cmd");

  $results .= `$deploy_cmd`;
  my $odFail = $?;

  ### if not OD fail and if any files need to be data deployed at all
  if (!$odFail) {
   $task->CallBack(0, "OpenDeploy Deployment Succeeded");
  }else{

   my $count;
   ### try five times
   for ($count = 1; $count <= 5; $count++) {

    &debug($count);
    #$results .= `$odcmd`;
    $results .= `$deploy_cmd`;
    &debug($results);
    $odFail = $?;
    &debug($odFail);

    if (!$odFail) {
     $task->CallBack(0, "Multiple OpenDeploy Deployment Succeeded");
    }else{
    # do nothing
    }

   }

   #print "od fails";
   open(RS,">$resultsfile");
   print RS qq~$results~;
   print RS "RUN: $deploy_cmd FOR MORE DETAILS";
   close RS;
   $task->CallBack(1, "OpenDeploy Deployment Failure: Check $resultsfile for more details");
   exit;
  }


 } # END IF STATEMENT
    } # END FOR STATEMENT

} #end sub deploy_files

### debug subroutine
sub debug
{
 #return if !$debug;
 my $message = shift;


 open (DEBUG, ">>$DEBUG_FILE") || exit;
 print DEBUG "\n";
 print DEBUG "$message";
 print DEBUG "\n";
 close DEBUG;
}

chriskmt

i think if i can access the checkboxes from the WFT file I can check to see what the user selected. "my @targets = param('DeployTo'); " doesn't work.

ISCBorisB

i think if i can access the checkboxes from the WFT file I can check to see what the user selected. "my @targets = param('DeployTo'); " doesn't work.

- To access Form's Value within "template_script" Tag you may use wft __VALUE__ Function.
Note that HTML Input name is irrelevant, it gets substituted with the TAG_info Entry Name.
(Eg, you must use 'iw_deploy_to' Accessor String, not "DeployTo' !)

- In the case of a checkbox __VALUE__ function returns an Array of values. So, if you've checked
for example 'dev' and 'prodTwo' boxes you will get:

# The following creates an Array @targets where $targets[0] eq 'dev' and $targets[1] eq 'prodTwo';
my @targets = __VALUE__('iw_deploy_to');

# This will create Job Variable 'test' with the (scalar) Value 'dev+prodTwo'
set_job_variable('test', join('+', __VALUE__('iw_deploy_to')));

Comprende?

Crsb

i think if i can access the checkboxes from the WFT file I can check to see what the user selected. "my @targets = param('DeployTo'); " doesn't work.

Try this if you want to achieve what you need with minimal changes.

keep the original code with radio buttons, then add third option for the radio item with value "devandqa" and named/label "both".

then add these lines to your ipl code:


    if ($deployTo eq "devandqa") {
       $servers[$serv_ctr] = "dev";
       $serv_ctr++;
       $servers[$serv_ctr] = "qa";
       $serv_ctr++;
    }

chriskmt

Thanks guys that definitely looks like enough to get me going.

chriskmt

I just want to understand the example ISCBorisB gave.

Lets say I wanted to use this:
my @targets = __VALUE__('iw_deploy_to');

I would define that in

---------------------------------------------
…
my @targets = __VALUE__('iw_deploy_to');

]]>
</template_script>

---------------------------------------------

How can I access targets from the ipl script? When I use:
&debug("to: $targets[0]");

in the ipl file, the debug script bombs and nothing gets printed. How can I send @targets to the ipl file?

ISCBorisB

I just want to understand the example ISCBorisB gave.

Lets say I wanted to use this:
my @targets = __VALUE__('iw_deploy_to');

I would define that in

---------------------------------------------
…
my @targets = __VALUE__('iw_deploy_to');

]]>
</template_script>

---------------------------------------------

How can I access targets from the ipl script? When I use:
&debug("to: $targets[0]");

in the ipl file, the debug script bombs and nothing gets printed. How can I send @targets to the ipl file?

You can for example pass captured values as External Task command parameter(s). Alternatively, you can set Job/Task Variables
in WFT and obtain them in the Script using GetVariable Methods of corresponding Classes (in Perl, TeamSite::WFworkflow and TeamSite::WFtask)

chriskmt

You can for example pass captured values as External Task command parameter(s).

like this:
<command v="__INSERT__($deploy_cmd); __TAG__('iw_deploy_to');"/>

this is what I find confusing, in the ipl file there is a parameter called "$deployTo" (is that predefined? it is not found anywhere else in the ipl or wft. The first time it is mentioned in the IPL file it looks like this 'my $deployTo = shift;') which seems to be retrieving the 'iw_deploy_to' value. Here is what I have found:

'&debug("$deployTo");' prints out correctly in the debugger file.

When more than one check is checked,
'&debug("$deployTo");' prints out "ARRAY …" which is still ok and deploy hangs, as is expected.

but when I use
'&debug("start deploy to array");'
'&debug("$deployTo[0]");'
it breaks, "start deploy to array" is the last thing printed in the debug file.

It also breaks if I use "__VALUE__('iw_deploy_to');" in the command node of the WFT.

ISCBorisB

Ok - simple things first... Both __VALUE__ and __TAG__ Functions belong to WFT Parser and may not be used outside of WFT Template.
Within 'template_script' Tag you should access TAG_info captured values with the __VALUE__ Function. Outside of it - with
the __TAG__ Function.

As for the rest - you must know Perl to do coding in Perl! If looking at the code you do not understand the semantics of something as rudimentary
as my $deployTo = shift; - I'm not sure I have enough time to explain Perl's Concept of Scalar/Array Context and why you get a scalar String
'ARRAY[some ID]' - and why it fails when you pass this String as a command parameter and try to use as Array

chriskmt

Ok - simple things first... Both __VALUE__ and __TAG__ Functions belong to WFT Parser and may not be used outside of WFT Template.
Within 'template_script' Tag you should access TAG_info captured values with the __VALUE__ Function. Outside of it - with
the __TAG__ Function.

As for the rest - you must know Perl to do coding in Perl! If looking at the code you do not understand the semantics of something as rudimentary
as my $deployTo = shift; - I'm not sure I have enough time to explain Perl's Concept of Scalar/Array Context and why you get a scalar String
'ARRAY[some ID]' - and why it fails when you pass this String as a command parameter and try to use as Array

So are you saying that the way this is being passed, it cannot be accessed as an array?

I do understand what shift does, I just was unclear of the connection between "$deployTo" and __TAG__('iw_deploy_to') because the first it is mentioned, is with shift.

ISCBorisB

So are you saying that the way this is being passed, it cannot be accessed as an array?

Ok, I'll try one more time...

The following will work for a scalar 'iw_deploy_to' Value.
<command v="__INSERT__($deploy_cmd); __TAG__('iw_deploy_to');"/>

However, if __TAG__('iw_deploy_to') evaluates to an Array, in the scalar Context it'll render something like that:
<command v="YourScript ARRAY(0xSomeHexDigits)"/>

Sure enough, in the totally different thread of External Task Execution this ARRAY parameter is just a String.
It is a signature of no longer existing Array Object from the long gone WFT Parser Process. Trying to use it
at all, much less as an array makes no sense.

If you want to pass an Array as the OS Command Parameter(s) you should build it with Array scalar Values like
"Command A B C..." with undefined number of parameters or alternatively use some sort of join and pass a single
parameter with a delimiter: "Command A+B+C..." and split it within code

Makes sense?

chriskmt

Try this if you want to achieve what you need with minimal changes.

keep the original code with radio buttons, then add third option for the radio item with value "devandqa" and named/label "both".

then add these lines to your ipl code:
    if ($deployTo eq "devandqa") {
       $servers[$serv_ctr] = "dev";
       $serv_ctr++;
       $servers[$serv_ctr] = "qa";
       $serv_ctr++;
    }

Thanks this worked out perfectly.

chriskmt

Ok, I'll try one more time...

The following will work for a scalar 'iw_deploy_to' Value.
<command v="__INSERT__($deploy_cmd); __TAG__('iw_deploy_to');"/>

However, if __TAG__('iw_deploy_to') evaluates to an Array, in the scalar Context it'll render something like that:
<command v="YourScript ARRAY(0xSomeHexDigits)"/>

Sure enough, in the totally different thread of External Task Execution this ARRAY parameter is just a String.
It is a signature of no longer existing Array Object from the long gone WFT Parser Process. Trying to use it
at all, much less as an array makes no sense.

If you want to pass an Array as the OS Command Parameter(s) you should build it with Array scalar Values like
"Command A B C..." with undefined number of parameters or alternatively use some sort of join and pass a single
parameter with a delimiter: "Command A+B+C..." and split it within code

Makes sense?

Yes it does and of the few suspicions I had, this was one of them, I just wasn't sure.

chriskmt

Ok thanks guys. I guess the thing that was tripping me up was that by the time the ipl script received the values of the checkboxes, it has been flattened into a string "ARRAY(-whatever-)". I assumed it was still an array.

Both solutions offered by you guys worked, I wanted to understand why the checkboxes were failing. Incase anyone else needs to do the same thing, here is what I did.

in '<template_script>' after the

'iw_deploy_to => [ html => ----checkbox inputs inside here---- ]'

I have
my $targets = join(':', __VALUE__('iw_deploy_to'));

then in the deploy '<externaltask>' workflow I added:
…
<variables>
<variable key="targets" value='__INSERT__($targets);'/>
</variables>
</externaltask>

In the IPL script i have :
my $getTargets = $task->GetVariable('targets');
my @targetSplit = split(/:/, $getTargets);

foreach (@targetSplit) {
if ($_ eq "dev") {
$servers[$serv_ctr] = "dev";
$serv_ctr++;
}
if ($_ eq "qa") {
## and so on for prod1 and prod2

Another foreach
for ($i=0; $i<$serv_ctr; $i++) {
if ($servers[$i] ne "0") {

##DO DEPLOY##
}
}

So it is a matter of flattening the checkbox array, sending it with the <variables> tags, then the ipl script splits the string and loops the array and creates another array for the deploy to loop through to deploy to each server.

This was great I learned a lot.