I have an issue with the way OD 5.5.1 returns log information. Specifically, when you run deployments using the iwodstart CLT from a script. In the old days, using iwdeploy, you could set a variable to the result of iwdeploy as such:
my
@deployresults = `iwdeploy ...`;
and then
@deployresults would contain all the detailed log info that resulted from the deployment. This was good, as I could parse this output for the word "ERROR" and report error information back to the user immediately.
With iwodstart, when you run it the same way:
my
@deployresults = `iwodstart ...`;
What you see when you print out
@deployresults is this:
Locating OpenDeploy service.
OpenDeploy server host: localhost, RMI registry port: 9173
Got OpenDeploy service.
>>>>>-- Start deployment ZERO_deploy_2129.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment ZERO_deploy_2129 finished:
ID: m60 Start time: Thu Aug 01 14:15:55 PDT 2002
Status: Completed
Which is essentially useless information. If I want to parse the detailed log info, I have to find the appropriate log file in .../opendeploy/OpenDeployNG/log, which is easy. Then parse the log. Unless I run the same deployment over and over. Then this log file simply appends a new log to the end of this file every time you run the deployment. This becomes a parsing nightmare.
What I'd like is to have the iwodstart CLT return the single instance of detailed log info like iwdeploy did. That would make parsing for errors very easy again.
Dave SmithSr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com
