Merge pull request codefresh-io#485 from codefresh-io/classic-pause-pipelines

Update pipeline settings

Author: NimRegev

_docs/administration/pipeline-settings.md

@@ -13,8 +13,28 @@ On this page, you can define global parameters for the whole Codefresh account r
 lightbox="true"
 file="/images/administration/pipeline-settings/pipeline-settings-ui.png"
 url="/images/administration/pipeline-settings/pipeline-settings-ui.png"
-alt="pipeline-settings"
-caption="pipeline-settings"
+alt="Pipeline settings"
+caption="Pipeline settings"
+max-width="80%"
+%}
+
+
+## Pause pipeline executions
+
+Pause builds for pipelines at the account level, for example, during maintenance.  
+
+* **Pause build execution** is disabled by default.  
+* When enabled:  
+  * New pipelines in the account are paused immediately. 
+  * Existing pipelines with running builds are paused only after the builds have completed execution.  
+* Paused pipelines are set to status Pending, and remain in this status until **Pause build execution** is manually disabled for the account.
+
+{% include image.html
+lightbox="true"
+file="/images/administration/pipeline-settings/pause-pipeline-enabled.png"
+url="/images/administration/pipeline-settings/pause-pipeline-enabled.png"
+alt="Pause Build Execution pipeline setting enabled"
+caption="Pause Build Execution pipeline setting enabled"
 max-width="80%"
 %}
 

_docs/configure-ci-cd-pipeline/monitoring-pipelines.md

@@ -66,7 +66,7 @@ The available filters are:
 * *Branch* - any of the available branches from the attached Git trigger.
 * *Committer* - person that made the commit that triggered the build.
 * *Environment* - which [environment]({{site.baseurl}}/docs/deploy-to-kubernetes/environment-dashboard/) was affected.
-* *Status* - success, error, in-progress, pending, terminated etc.
+* *Status* - success, error, in-progress, pending, terminated etc. A Pending status can also indicate that [pipeline build execution has been paused]({{site.baseurl}}/docs/administration/pipeline-settings/#pause-pipeline-executions) for the account.
 * *Trigger type* - what type of trigger was responsible for this build
 * *Git event* - in the case of [git triggers]({{site.baseurl}}/docs/configure-ci-cd-pipeline/triggers/git-triggers/) the exact event
 
@@ -208,6 +208,7 @@ You can also search the logs by clicking at the magnifying glass icon at the top
 
 > Note: The max size each step can log is around 20MB, and 100MB for the whole build. After that, the system will stop logging, but the build execution will continue.
 
+
 ### Reviewing the yaml for the pipeline
 
 From the step details you can also click on the yaml tab to see the yaml segment for that individual step: