It would be really nice to be able to tell the Action Output Monitor to not only Fail action if ... but to actually Fail&Abort action if ... because when you hav a long-running external executable it really doesn't make sense to wait on it once it has been determined to have failed via its logging output.
(I have checked with FB7 and I have found no workaround for this problem neither via the Script Actions nor anything in Action Studio.)
Do you have any plans for this? Can it be achieved via a Script Event or via a custom Action created in ActionStudio?
It’s a good idea, I’ll add it to the todo list. I don’t believe it can be done via script as we don’t fire any events when the output monitors are run (too much overhead).
Posted By Vincent Parrett on 10 Jun 2011 06:46 AM It's a good idea, I'll add it to the todo list. I don't believe it can be done via script as we don't fire any events when the output monitors are run (too much overhead).
Thanks!
I didn't mean an event for the output monitor. As far as I can tell, when running an executable it would theoretically be possible to implement an output monitor myself in the script action as there is a callback for each logged line (OnStatusMessage event) and I could just fail the Action there.
It is however not possible (you do not expose a script function or the neccessary info) to abort/kill the process that was spawned by finalbuilder.
Maybe it would make sense to make the Process ID/Handle of the external process availabe to the action. This way it would be possible to interact with the process from the script. (e.g., kill it via vbscript/WMI)