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 5.6 dnrDeploymentJob response code="-2"

ProfessorX

OD 5.6 dnrDeploymentJob response code="-2"

Using a WF to call OD with DNR this works correctly on failure.
<deployment transactional="yes" >
<execDeploymentTask useDefinition="ski_documents" downRev="" >
<deployNRun >
<dnrDeployment location="source" when="after" state="success" >
<script cmd="D:/progra~1/interwoven/teamsite/iw-perl/bin/iwperl

/progra~1/interwoven/teamsite/httpd/iw-bin/razf_deploy_metadata_test.ipl $wfid $taskid $area" as="ABC\admin" where="" async="no" >
</script>
</dnrDeployment>
</deployNRun>
</deployment>
OD LOG ##########################################
(2) client: Executed script [D:/progra~1/interwoven/teamsite/iw-perl/bin/iwperl /progra~1/interwoven/teamsite/httpd/iw-bin/razf_deploy_metadata_test.ipl 52506 52520 Y:/default/main/SKI/WORKAREA/aciliberto] where [] as [abc\skiadmin] FAILED
ERROR: client_after_deploy DNR script failed during commit phase.
ERROR: Failed to deploy local_directory[.] of area[Y:\default\main\SKI\STAGING] for filelist[D:\PROGRA~1\INTERW~1\TeamSite\tmp\filelist.52506]
ERROR: Failed 1 of 1 filelists
client: ROLLBACK Transactional Deployment

My WF transitioned to the "failure" task fine.
But doesn't work correctly using a Deployment-Level Trigger
<deployment transactional="yes" >
<execDeploymentTask useDefinition="ski_documents" downRev=""/>
<dnrDeploymentJob location="source" when="after" state="success">
<script cmd="D:/progra~1/interwoven/teamsite/iw-perl/bin/iwperl

/progra~1/interwoven/teamsite/httpd/iw-bin/razf_deploy_metadata_test.ipl $wfid $taskid $area" as="ABC\skiadmin" where="" async="no" >
</script>
</dnrDeploymentJob>
</deployment>
OD LOG ##########################################
LIB: Locale=[English_UnitedStates.MS1252@Binary]
(2) Executed script [D:/progra~1/interwoven/teamsite/iw-perl/bin/iwperl /progra~1/interwoven/teamsite/httpd/iw-bin/razf_deploy_metadata_test.ipl 52472 52486 Y:/default/main/SKI/WORKAREA/aciliberto] where [] as [abc\skiadmin] FAILED
ENG: 2003-08-22 15:32:45 EDT GMT-04:00 Thread-26 ***ERROR - Job D=m12Deployment=SKI_RF_UAT_DOC_TEST52486
UnSuccessful before-all DNR Execution ..
[d:\Interwoven\OpenDeployNG\log\src.SKI_RF_UAT_DOC_TEST52486.ski_documents.abc.to.uatski_skip00.log]

But yet my WF transitions to the "success" task

My script is definitely failing and I tired transactional="yes" and transactional="no" (I saw a post regarding Deployment-Level Triggers not supporting transactional)

OD 5.6 SP 1 patch nt_od560SP1_p43589_p43628

The Professor-

Find more posts tagged with

Comments

Migrateduser

According to the OD 5.6 SP1 Release Notes, p. 51, a deployment will return status code 0 regardless of whether dnrDeploymentJob returns -2. So I think the behavior you are seeing is consistent with that.

I believe only trigger points within the sender-receiver connection window currently influence the deployment status code.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

bboyle

spot on!

but I would really like to see this stuff in the manual, not the release notes. This is a general comment on Interwoven documentation: less fragmentation, put it in the manual!!!

I went and read the release notes after reading this post and it really is documented well in there, just too obscure to find (imho).

but devnet forums come through again [insert "thumbs up" icon here]

Migrateduser

Fyi, the OD 5.6 docs were updated in November 2003. At that time, much of the fragmented details found in the release notes were rolled into the proper manuals.

The updated docs have a "b" in the file name, for example od.560b.admin.pdf, and "November 2003" at the bottom of the copyright page.

The latest docs are available through the support site.

Cheers,

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

bboyle

Hey thanks, that's great!

Sorry I didn't realise it had been updated... it often lags behind the product release and I forget to check. I'm not sure we get notification of documentation updates like we for product releases... could easily be something I missed though.

Which is bad because I'm very fond of the updated documentation, it really helps. The docs ppl should get a big pat on the back for the great job they're doing.

And if there's any way that documentation could be ready in time for updates, so it could all be released together ... well, I'd really appreciate that. It may seem a minor thing but it really makes a difference. I guess we get release notes but not quite the same thing.

Just my opinion.

Migrateduser

Thanks for the comments. I agree it would be optimal if we could rev the docs with each service pack, maintenance release, platform port, jumbo patch, etc. Since we haven't been able to do that in most cases, any relevant updates end up in a release notes doc, and are subsequently rolled into the main docs next time they are revved.

So, the best thing for now would be to check the support site periodically for updated docs. And to ask Tech Support to let you know when new doc releases occur (typically as part of a particular release vehicle.)

Cheers,

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

PaulW

I had the following xml in my OD config file:

<dnrDeployment location="source"
when="after"
state="success"
triggerpoint="transfer">

and when my script returned: "<response code=\"-2\"/>\n" it still did not cause the OpenDeploy job to fail. I looked in od.560b.admin.pdf and the table on page 185 seems to indicate that a -2 response should cause OpenDeploy to rollback based on the above XML. I am running a transactional deployment. async="no".

I am running OpenDeploy5.6. with no service pack, because the box is shared, so we have no control over the software we install on it.

What else could I be missing? Any help would be greatly appreciated

PaulW

Gee I'm a clown. Sorry.

Even thoguh I read the reponse code needs to be output to STDOUT, I was trying to exit my script by:
exit "<response code=\"-2\" />";

Instead I now do:
print "<response code=\"-2\" />"; #failure

and it works.