From 438597dcc1ee5b6aee30abca32102e0d5b385cdf Mon Sep 17 00:00:00 2001 From: Priti Desai Date: Fri, 5 Feb 2021 12:03:22 -0800 Subject: [PATCH] updating doc for using finally in pipeline results Recently Scott fixed the bug in which pipeline results emitted the result reference variable as is in case of a missing result. Updating the doc to reflect those changes when a result reference from finally is used in pipeline result. --- docs/pipelines.md | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/docs/pipelines.md b/docs/pipelines.md index 853bd3badf4..a5e5cb1e2ef 100644 --- a/docs/pipelines.md +++ b/docs/pipelines.md @@ -1069,16 +1069,8 @@ Final tasks can emit `Results` but results emitted from the final tasks can not value: $(finally.check-count.results.comment-count-validate) ``` -In this example, `PipelineResults` is set to: +In this example, `pipelineResults` in `status` will exclude the name-value pair for that result `comment-count-validate`. -``` -"pipelineResults": [ - { - "name": "comment-count-validate", - "value": "$(finally.check-count.results.comment-count-validate)" - } -], -``` ## Using Custom Tasks