#1
|
|||
|
|||
"Fail but continue" option
Would like an option for a step that has failed, to continue trying to build other things but fail the overall build.
We have a complex product to build. Some of it is dependent on common elements but there are many independent parts. Thus we want to try building as much as possible, not stop at the first failure - but even one failed step does mean the build failed. Likewise, at the end of it, I would like to see a coherent report of "these items failed" ... which is kind of hard to get at the moment. As discussed by another user: http://www.kinook.com/Forum/showthre...l+AND+continue |
#2
|
|||
|
|||
We'll consider providing a built-in way to track the overall status of a build (whether any steps failed even if the build continued).
For now, you could use a project-level step done script event to store a flag in a temporary macro for whether any steps failed (but marked to continue building) during the build, and then at the end of the build, fail the build (conditionally build an Exit step if that flag is set). http://www.kinook.com/VisBuildPro/Ma...riptevents.htm You can report on all failed steps in a build by using XML log file format, then creating a report with the Transform XML Log action, filtering on failed steps. http://www.kinook.com/VisBuildPro/Manual/loggingopt.htm http://www.kinook.com/VisBuildPro/Ma...gfiltertab.htm |
#3
|
|||
|
|||
OK, thanks. I have done this now.
Also used the event to log failed items to a separate file, which seems less drastic than changing the entire logging format to XML just to get this info. Seems a bit clunky but does work. Is there any reason why I need to use a ScriptDone event, rather than just a failure step? |
#4
|
|||
|
|||
No, a failure step is certainly another good (maybe better) way to do that.
|
#5
|
|||
|
|||
This is implemented in v8.0.
|
#6
|
|||
|
|||
Wow, actually following up on the original thread! Very nice!
Regards Aaron |
|
|