Nested packages Error Mode precedence
Hi all,
We are having an issue with using "Error Mode: Continue" taking precedence in a package that nests other packages.
The individual packages have "Error Mode: Stop Deployment with Error" because normally, I actually care about 1605 errors. However, in the package we're building on, we don't care that step 1: Nested package X might fail; that's why we're gonna proceed to step 2. (This package is a shotgun method of "try to uninstall any version of this application that may or may not be on the target machines".)
We've set "Error Mode: Continue" in step 1 in the master package, but it's still stopping deployment on error anyway.
Is this working as intended or a bug? What is the order of precedence for Error Mode Stop Deployment with Error?
Comments
I can confirm this, i face this bug with nested packages since Deploy 17.