# Feature request: Inspect the build log

**URL:** https://www.finalbuilder.com/forums/t/feature-request-inspect-the-build-log/5042
**Category:** Feature Requests
**Created:** [August 12, 2013, 10:13am UTC](https://www.finalbuilder.com/forums/t/feature-request-inspect-the-build-log/5042 "2013-08-12T10:13:24Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![sgjennings](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sgjennings/32/141_2.png) [@sgjennings](https://www.finalbuilder.com/forums/u/sgjennings)
#### Post date: [August 12, 2013, 10:13am UTC](https://www.finalbuilder.com/forums/t/feature-request-inspect-the-build-log/5042/1 "2013-08-12T10:13:24Z")

</div>

One action in our build process is to call MSDeploy. Unfortunately, MSDeploy always returns exit code 0 regardless of whether the deploy failed or not, so Continua always believes the action succeeded.

What I would like to do is search the MSDeploy action's build log for "Error Count: \d+". If this line exists, it means the deploy failed. If the line is absent, the deploy succeeded. I think this could be implemented with a variable such as $Build.Log$ that represents "the build log at the point this variable is being evaluated". For example, a stage's actions might look like this:

- MSDeploy Action  
- If $Build.Log$ matches "Error Count: \d+"  
--- Stop build as failure  
- Else  
--- Continue with build

Another way might be to add a "Success Conditions" tab on every action, and create an $Action.Log$ variable that's available on this screen. This would look similar to the Stage Gate settings, it would be a list of left and right values that must evaluate to true in order for the action to considered a success. For example, in this situation I would add this:

Left Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Operator&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Right Value  
$Action.Log$&nbsp;&nbsp;&nbsp;&nbsp; does not match&nbsp;&nbsp;&nbsp;&nbsp; Error Count: \d+&nbsp;

&nbsp;

Thank you for your consideration.

---

<div class="post-metadata">

### Author: ![christian.leh](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/c/67e7ee/32.png) [@christian.leh](https://www.finalbuilder.com/forums/u/christian.leh)
#### Post date: [August 13, 2013, 7:43am UTC](https://www.finalbuilder.com/forums/t/feature-request-inspect-the-build-log/5042/2 "2013-08-13T07:43:52Z")

</div>

+1 (like FinalBuilder). Additionally the option to parse the output and set variables.

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [August 14, 2013, 1:19am UTC](https://www.finalbuilder.com/forums/t/feature-request-inspect-the-build-log/5042/3 "2013-08-14T01:19:33Z")

</div>

What you are describing sounds like the Output Monitor feature in FinalBuilder : [http://help.finalbuilder.com/Index.htm?action\_output\_monitors.htm](http://help.finalbuilder.com/Index.htm?action_output_monitors.htm)   
  
 This is something we would to add to Continua CI.