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; } } }

OD: Is there a way to confirm files are deployed?

andrew_yeo

There have been situation where my Production Web Server got hung. Such that files submitted were deployed at the STAGING but did not successfully deployed the the PWS?

What options are there to close the loop? such that i can be sure the files are deployed at the Production Server end, without of'cos doing a manual check online

Find more posts tagged with

Comments

Gerard

I would suggest to use a transactional type of deployment: either it fails or it succeeds completely. You have to check the log of course to see if it succeeded....

Gerard

Migrateduser

Or use a deploy and run (DNR) script to send yourself an email notification.

Migrateduser

When I run Open Deploy using a workflow (externaltask), I send all my deploy results to my own debug log and keep all of those for 30 days as an archive. I also scan the output for lines that contain the words "ERROR" or "warning" and move to a "Deploy Failed" task in my workflow and notify all parties that something went wrong. That way I know when my deployments have failed and I can quickly check my debug log. At that point, the workflow is in a state where we can retry the deployment if the problem is easily fixable or end the job if it's a fatal error.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

andrew_yeo

is there something wrong with the docs on OD, here's what i put for the DeployNRun in the config file and it just doesn't work....

..
<deployment transactional="yes" >
<execDeploymentTask useDefinition="MYDEFINITIONNAME" >

<deployNRun>
<dnrDeployment
location="source"
when="after"
state="success" >
<script cmd="C:\\od-home\\bin\\email_to_admin.cmd" />
</dnrDeployment>
</deployNRun>
</execDeploymentTask>
..

tried single slash...tried full paths, tried specifying "C:\Winnt\system32\cmd.exe", please tell me what else did i missed.. <sigh...>

tvaughan

That looks good.

I'm on Solaris, so I don't have to worry about backslashes and what-not. The only difference between mine and yours is that I've got an asynch="no" section right after my command string, and right before my closing "/>" :


< deployment transactional="yes"  >
      < execDeploymentTask  useDefinition="Forward2Prod" >
          < deployNRun>
              < dnrDeployment  location="target"
                              when="after"
                              state="success">
                  < script  cmd="$stage_script_name^"
                           async="no"
                           />
              < /dnrDeployment>
          < /deployNRun>
      < /execDeploymentTask>
  < /deployment>
< /pre>

Good luck,
Tom

Migrateduser

Is the command being executed but not receiving email, or command not executed at all ?

If not executed at all, do the OD logs (OpenDeployNG/logs) on the source side give any clues ?

andrew_yeo

gosh...i really have no clues whether it did try to run at all but i did run the script offline from command prompt, it runs well.

andrew_yeo

In windows, this works:

<execDeploymentTask useDefinition="MYDEFINITIONNAME" >
<deployNRun>
<dnrDeployment location="target" when="after" state="always" >
<script cmd="c:\od-home\bin\email_to_admin.cmd" />
</dnrDeployment>
</deployNRun>
</execDeploymentTask>

fuzzy

Hi Dave,
I do exactly what you do. The deployment is started in a workflow (so the user selects the editions and different deployment options) and as part of the workflow I also do a reverse deployment to bring back all log files and then I parse them by looking for error and warning and send out email to appropriate parties if errors have occured.
I.e database connection - DBA and ITO group and so on.
I am in the process of upgrading to OD 5.5.2 and the log files generated by opendeploy are totaly different
how do you get arround this problem?
regards

Migrateduser

OD 5.5.1 has some nice features, like the GUI, but they took away some really nice features as well, like the GRC reporting and the command line tool returning the log info. So now it's a little trickier to parse the logs. For one thing, you have to go find the log file, which is easy but the log name is enormous, so you have to use a little string manipulation to make sure you look at the correct log file. Nothing hard, just tedious. Then you can parse that log file the same way you did before. It would just be nice if the iwodstart CLT returned useful information like the old CLT did. You really can't use the **** the iwodstart command returns.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

Rather than trying to parse the physical log - why not parse the in-memory XML log that is passed into the DNR on STDIN? You can make use of the IWODHOME/solutions/perl/IWXML.pm - and there's also some stuff under IWODHOME/solutions/java (though I've never used it so I cannot comment too much on it).

OpenDeploy 5.6 (coming soon to a support site near you :-) will have built-in reporting functionality - though I'm not sure if that will help you in this particular case (it might, since you could perhaps do a query of the DB to find specific information?)

--fish
(Interwoven Senior Technical Consultant)

Bubas_IWOV

Fish,

Can you please send me any example of a script that reads the Opendeploy in memory logs in windows?

Regards
Bruno

iwovGraduate

As already mentioned earlier, there are examples for this shipped with the product. Look at ODHOME/OpenDeployNG/solutions directory
What version of OpenDeploy do you have ?

Bubas_IWOV

Hi,

none of them seem to work in windows.

Bruno

Adam Stoller

I posted a simple script on one of the other threads - but for sake of completeness ... here it is too:#!c:/path/to/your/perl -w
my $logfile = "c:/path/to/your/logfile";
if (open(OUT, ">$logfile")){
print OUT while(<STDIN>);
close(OUT);
}
exit(0);

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com