NPM warnings trigger plan failure

[Guest]

NPM logs its warnings to stderr, and it appears that any time this occurs during an Execute Process task, the plan aborts and reports failure.

Short version: is there a way to have BuildMaster not treat stderr output as a failure and instead only look at the exit code?

I can suppress the warning messages when executing NPM and Bower, though I have a third process to execute (ember-cli) where I can't disable the warnings. My temporary "fix" at the moment is to wrap the task in a Try/Catch block, but now I've lost the ability to detect when real errors occur. That's bad, naturally.

Thanks, and let me know if any more detail is needed.

Product: BuildMaster
Version: 5.0.11

[Guest]

The Execute Process Operation has some options that you may find useful in this case. For example:

exec npm 
(
    Arguments: something,
    ErrorOutputLogLevel: Information
);

[Guest]

Aha! That's the ticket -- setting ErrorOutputLogLevel to "Warning" is just what I was looking for. For some reason I had thought the option would do the inverse (e.g. elevate warnings to errors).

Thanks a ton for the help,
-J