Merge pull request #1504 from abayer/jenkins-41239

[JENKINS-41239] Add doc for new cleanup post condition.
jenkins-infra · Apr 18, 2018 · 5c434e8 · 5c434e8
2 parents 92e468e + c8c7bce
commit 5c434e8
Showing 1 changed file with 8 additions and 4 deletions.
diff --git a/content/doc/book/pipeline/syntax.adoc b/content/doc/book/pipeline/syntax.adoc
@@ -258,10 +258,11 @@ The `post` section defines one or more additional <<declarative-steps,steps>>
 that are run upon the completion of a Pipeline's or stage's run (depending on
 the location of the `post` section within the Pipeline). `post` can support any of
 of the following <<post-conditions, post-condition>> blocks: `always`,
-`changed`, `fixed`, `regression`, `aborted`, `failure`, `success`, and `unstable`.
-These condition blocks allow the execution of steps inside each condition
-depending on the completion status of the Pipeline or stage.
-The condition blocks are executed in the order shown below. 
+`changed`, `fixed`, `regression`, `aborted`, `failure`, `success`,
+`unstable`, and `cleanup`. These condition blocks allow the execution
+of steps inside each condition depending on the completion status of
+the Pipeline or stage. The condition blocks are executed in the order
+shown below. 
 
 [cols="^10h,>90a",role=syntax]
 |===
@@ -297,6 +298,9 @@ run has a "success" status, typically denoted by blue or green in the web UI.
 `unstable`:: Only run the steps in `post` if the current Pipeline's or stage's
 run has an "unstable" status, usually caused by test failures, code violations,
 etc. This is typically denoted by yellow in the web UI.
+`cleanup`:: Run the steps in this `post` condition after every other
+`post` condition has been evaluated, regardless of the Pipeline or
+stage's status.
 
 [[post-example]]
 ===== Example