changed failure success unstable aborted Example stages Only run the steps in  post  if the current Pipeline’s or stage’s run has a different completion status from its previous run. Only run the steps in  post  if the current Pipeline’s or stage’s run has a "failed" status, typically denoted by red in the web UI. Only run the steps in  post  if the current Pipeline’s or stage’s run has a "success" status, typically denoted by blue or green in the web UI. 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. Only run the steps in  post  if the current Pipeline’s or stage’s run has an "aborted" status, usually due to the Pipeline being manually aborted. This is typically denoted by gray in the web UI. ① Conventionally, the  post  section should be placed at the end of the Pipeline. ② Post-condition blocks contain steps the same as the [steps] section. Containing a sequence of one or more [stage] directives, the  stages  section is where the bulk of the "work" described by a Pipeline will be located. At a minimum it is recommended that  stages contain at least one [stage] directive for each discrete part of the continuous delivery process, such as Build, Test, and Deploy. 86 // Declarative // pipeline { agent any stages { stage('Example') { steps { echo 'Hello World' } } } post {  ① always {  ② echo 'I will always say Hello again!' } } } // Script //