MHolmes
09-30-2004, 03:39 PM
Our build process is a bit unique in that we log our failed build steps to some various media (via a COM component that I wrote in C# w/ COM interop). Basically, when a step fails, we don't want the Visual Build build process to stop, we simply want to use a script to instanciate this component, call a method on it, and continue with the build.
The caveat to this is that there are certain projects we have that WILL fail the entire build. We keep our "what to build list" in special text files that we read in using Visual Build's facilities. It's easy enough to know what is and isn't critical, and what to build.
The problem is that Visual Build sets the Step.BuildStatus value to 0 (or succesful) if the build succeeds OR it's set to ignore failure. This is an issue with us. We need to be able to mark the node as "Ignore Fail", but still be able to detect relevant failure in the event scripts.
Is this possible? This is stopping me from really stream lining our build process...
The caveat to this is that there are certain projects we have that WILL fail the entire build. We keep our "what to build list" in special text files that we read in using Visual Build's facilities. It's easy enough to know what is and isn't critical, and what to build.
The problem is that Visual Build sets the Step.BuildStatus value to 0 (or succesful) if the build succeeds OR it's set to ignore failure. This is an issue with us. We need to be able to mark the node as "Ignore Fail", but still be able to detect relevant failure in the event scripts.
Is this possible? This is stopping me from really stream lining our build process...