Version Differences for Status Scripts

(AHPSCRIPTS-37 & AHPSCRIPTS-36 Combo - - Commented out inspectors)
(Set a Build Life Status on Any Failed Test (Assign Status Step))
Line 92:
  * This script goes in an '''Assign Status''' step.    * This script goes in an '''Assign Status''' step. 
  * A combination of the practices in AHPSCRIPTS-36 & AHPSCRIPTS-37 are being used. In this script (which is placed in an '''Assign Status''' step), the tests on the build life will be analyzed, and any that are found to have failures will cause a ''failure'' status to be assigned; otherwise a ''success'' will appear.    * A combination of the practices in AHPSCRIPTS-36 & AHPSCRIPTS-37 are being used. In this script (which is placed in an '''Assign Status''' step), the tests on the build life will be analyzed, and any that are found to have failures will cause a ''failure'' status to be assigned; otherwise a ''success'' will appear. 
    + * It should be noted that '''post-processing scripts''' will still complete successfully if the status was assigned. Therefore, it may be necessary to follow-up with an additional evaluate script step to check the output of the previous step:  
    + **<pre>import com.urbancode.anthill3.runtime.scripting.helpers.*;  
    + import com.urbancode.anthill3.domain.status.*;  
    + import com.urbancode.anthill3.domain.buildlife.*;  
       
    + Status fail = StatusLookup.getStatusByName("Failed Tests");  
    + BuildLife current = BuildLifeLookup.getCurrent();  
       
    + if(current.hasStatus(fail)){  
    + commandOutput.println("Failed Status detected!!!");  
    + throw new Exception();  
    + } else return null;  
       
    + </pre>  
       
  ==== AHPSCRIPTS-37 & AHPSCRIPTS-36 Combo ====    ==== AHPSCRIPTS-37 & AHPSCRIPTS-36 Combo ====