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

DnR error handling question

Dwayne

OK, now it's my turn for a question.

(I don't think this matters for this question, but ...)
OS: W2K3
TS: 5.5.2 (but moving to 6.1)
OD: 5.6 (but moving to 6.0)

Does anyone know what OD's behavior is in the case of a file-based DnR script where the script sets a non-fatal error? I know that it can abort the deployment with a -2 status. But -1 is a non-fatal error. If this is used on a file-based deployment, will it prevent the deployment of that file (if when="before") and/or undo the deployment (if when="after")? Or is that just logged as informational, but the deployment continues unchanged?

--

Current project: TS 5.5.2/6.1 W2K

Find more posts tagged with

Comments

Migrateduser

I believe the deployment continues unchanged.

Dwayne

That's what I thought - I was just hoping otherwise.

I've have tested it myself, but I don't have an instance of OD sitting around that I can "play with" right now. Thanks for the response.

--

Current project: TS 5.5.2/6.1 W2K

bboyle

not very elegant, but you could use a wrapper perl script to detect the state you're interested in and return a -2 status to OpenDeploy.

we have a single "status" script which we use to run any other scripts that we want to communicate back to OpenDeploy ... this allows the other scripts to simply die or fail in the usual way and the status script will check their exit status and print the XML required to actually communicate that status to OpenDeploy.