Version Differences for Quiet Periods and Their Purpose

(Quiet Periods that are Successful)
(Quiet Periods that are Successful)
Line 16:
  * '''No Quiet Period''' + Run Quiet Period = Changes Picked Up...Get Changelog skipped in Quiet Period    * '''No Quiet Period''' + Run Quiet Period = Changes Picked Up...Get Changelog skipped in Quiet Period 
  ** Since the quiet period is skipped (due to no quiet period being present at the project level), this will always result in anthill thinking changes are occurring in a project, which will eventually produce a build. Whether this is to be desired or not is up to the operator.    ** Since the quiet period is skipped (due to no quiet period being present at the project level), this will always result in anthill thinking changes are occurring in a project, which will eventually produce a build. Whether this is to be desired or not is up to the operator. 
    + *** <pre>Requested by trigger  
    + Skipping Quiet Period  
    + Build is Needed due to:  
    + Source Change: true  
    + Dependency Change: false  
    + Build Forced: false  
    + </pre>Note that it is ''implied'' that there are '''always changes''' when there is no quiet period  
    + <br>  
    + <br>  
  * Changelog QP + Run Quiet Period = Changes Picked Up...Get Changelog ran in Quiet Period    * Changelog QP + Run Quiet Period = Changes Picked Up...Get Changelog ran in Quiet Period 
  ** This is a successful quiet period. The quiet period runs and determines if changes are present or not in the repository, and will create a new build life accordingly from it.    ** This is a successful quiet period. The quiet period runs and determines if changes are present or not in the repository, and will create a new build life accordingly from it. 
    + *** <pre>Requested by trigger  
    + Source Changes Found  
    + Build is Needed due to:  
    + Source Change: true  
    + Dependency Change: false  
    + Build Forced: false  
    + </pre>