Merge branch 'master' of https://github.com/tektoncd/pipeline into po…

…d_informer

docs/pipelines.md

@@ -12,21 +12,36 @@ weight: 3
   - [Specifying `Workspaces`](#specifying-workspaces)
   - [Specifying `Parameters`](#specifying-parameters)
   - [Adding `Tasks` to the `Pipeline`](#adding-tasks-to-the-pipeline)
-    - [Using Tekton Bundles](#tekton-bundles)
+    - [Tekton Bundles](#tekton-bundles)
     - [Using the `from` parameter](#using-the-from-parameter)
     - [Using the `runAfter` parameter](#using-the-runafter-parameter)
     - [Using the `retries` parameter](#using-the-retries-parameter)
-    - [Guard `Task` execution using `When Expressions`](#guard-task-execution-using-whenexpressions)
+    - [Guard `Task` execution using `WhenExpressions`](#guard-task-execution-using-whenexpressions)
     - [Guard `Task` execution using `Conditions`](#guard-task-execution-using-conditions)
     - [Configuring the failure timeout](#configuring-the-failure-timeout)
   - [Using variable substitution](#using-variable-substitution)
   - [Using `Results`](#using-results)
-    - [Passing one Task's `Results` into the `Parameters` of another](#passing-one-tasks-results-into-the-parameters-of-another)
+    - [Passing one Task's `Results` into the `Parameters` or `WhenExpressions` of another](#passing-one-tasks-results-into-the-parameters-or-whenexpressions-of-another)
     - [Emitting `Results` from a `Pipeline`](#emitting-results-from-a-pipeline)
   - [Configuring the `Task` execution order](#configuring-the-task-execution-order)
   - [Adding a description](#adding-a-description)
   - [Adding `Finally` to the `Pipeline`](#adding-finally-to-the-pipeline)
+    - [Specifying `Workspaces` in Final Tasks](#specifying-workspaces-in-final-tasks)
+    - [Specifying `Parameters` in Final Tasks](#specifying-parameters-in-final-tasks)
+    - [Consuming `Task` execution results in `finally`](#consuming-task-execution-results-in-finally)
+    - [`PipelineRun` Status with `finally`](#pipelinerun-status-with-finally)
+    - [Using Execution `Status` of `pipelineTask`](#using-execution-status-of-pipelinetask)
+    - [Known Limitations](#known-limitations)
+      - [Specifying `Resources` in Final Tasks](#specifying-resources-in-final-tasks)
+      - [Cannot configure the Final Task execution order](#cannot-configure-the-final-task-execution-order)
+      - [Cannot specify execution `Conditions` in Final Tasks](#cannot-specify-execution-conditions-in-final-tasks)
+      - [Cannot configure `Pipeline` result with `finally`](#cannot-configure-pipeline-result-with-finally)
   - [Using Custom Tasks](#using-custom-tasks)
+    - [Specifying the target Custom Task](#specifying-the-target-custom-task)
+    - [Specifying parameters](#specifying-parameters-1)
+    - [Specifying workspaces](#specifying-workspaces-1)
+    - [Using `Results`](#using-results-1)
+    - [Limitations](#limitations)
   - [Code examples](#code-examples)
 
 ## Overview
@@ -788,7 +803,7 @@ spec:
           value: "someURL"
 ```
 
-#### Consuming `Task` execution results in `finally`
+### Consuming `Task` execution results in `finally`
 
 Final tasks can be configured to consume `Results` of `PipelineTask` from the `tasks` section:
 
@@ -883,7 +898,7 @@ For an end-to-end example, see [`status` in a `PipelineRun`](../examples/v1beta1
 
 ### Known Limitations
 
-### Specifying `Resources` in Final Tasks
+#### Specifying `Resources` in Final Tasks
 
 Similar to `tasks`, you can use [PipelineResources](#specifying-resources) as inputs and outputs for
 final tasks in the Pipeline. The only difference here is, final tasks with an input resource can not have a `from` clause
@@ -914,13 +929,13 @@ spec:
               - tests
 ```
 
-### Cannot configure the Final Task execution order
+#### Cannot configure the Final Task execution order
 
 It's not possible to configure or modify the execution order of the final tasks. Unlike `Tasks` in a `Pipeline`,
 all final tasks run simultaneously and start executing once all `PipelineTasks` under `tasks` have settled which means
 no `runAfter` can be specified in final tasks.
 
-### Cannot specify execution `Conditions` in Final Tasks
+#### Cannot specify execution `Conditions` in Final Tasks
 
 `Tasks` in a `Pipeline` can be configured to run only if some conditions are satisfied using `conditions`. But the
 final tasks are guaranteed to be executed after all `PipelineTasks` therefore no `conditions` can be specified in

go.mod

@@ -4,39 +4,52 @@ go 1.13
 
 require (
 	cloud.google.com/go/storage v1.11.0 // indirect
+	github.com/Azure/azure-sdk-for-go v50.2.0+incompatible // indirect
+	github.com/Azure/go-autorest/autorest v0.11.17 // indirect
+	github.com/Azure/go-autorest/autorest/adal v0.9.10 // indirect
+	github.com/Azure/go-autorest/autorest/to v0.4.0 // indirect
+	github.com/Azure/go-autorest/autorest/validation v0.3.1 // indirect
 	github.com/GoogleCloudPlatform/cloud-builders/gcs-fetcher v0.0.0-20191203181535-308b93ad1f39
+	github.com/aws/aws-sdk-go v1.37.1 // indirect
 	github.com/cloudevents/sdk-go/v2 v2.1.0
+	github.com/docker/cli v20.10.2+incompatible // indirect
+	github.com/docker/docker v20.10.2+incompatible // indirect
 	github.com/emicklei/go-restful v2.15.0+incompatible // indirect
 	github.com/ghodss/yaml v1.0.0
 	github.com/go-openapi/spec v0.20.2
+	github.com/gogo/protobuf v1.3.2 // indirect
 	github.com/google/go-cmp v0.5.4
-	github.com/google/go-containerregistry v0.4.1-0.20210127165842-51f01e739161
-	github.com/google/go-containerregistry/pkg/authn/k8schain v0.0.0-20210127165842-51f01e739161
+	github.com/google/go-containerregistry v0.4.1-0.20210128200529-19c2b639fab1
+	github.com/google/go-containerregistry/pkg/authn/k8schain v0.0.0-20210129212729-5c4818de4025
+	github.com/google/gofuzz v1.2.0 // indirect
 	github.com/google/uuid v1.1.2
+	github.com/googleapis/gnostic v0.5.3 // indirect
 	github.com/hashicorp/go-multierror v1.1.0
 	github.com/hashicorp/golang-lru v0.5.4
 	github.com/jenkins-x/go-scm v1.5.117
 	github.com/mitchellh/go-homedir v1.1.0
 	github.com/nbio/st v0.0.0-20140626010706-e9e8d9816f32 // indirect
-	github.com/onsi/gomega v1.10.3 // indirect
 	github.com/pkg/errors v0.9.1
+	github.com/sirupsen/logrus v1.7.0 // indirect
 	github.com/tektoncd/plumbing v0.0.0-20201021153918-6b7e894737b5
 	go.opencensus.io v0.22.5
 	go.uber.org/zap v1.16.0
+	golang.org/x/crypto v0.0.0-20201221181555-eec23a3978ad // indirect
 	golang.org/x/mod v0.4.1 // indirect
-	golang.org/x/oauth2 v0.0.0-20201208152858-08078c50e5b5
-	golang.org/x/sys v0.0.0-20210124154548-22da62e12c0c // indirect
+	golang.org/x/oauth2 v0.0.0-20210126194326-f9ce19ea3013
+	golang.org/x/term v0.0.0-20201210144234-2321bbc49cbf // indirect
+	golang.org/x/time v0.0.0-20201208040808-7e3f01d25324 // indirect
 	golang.org/x/tools v0.1.0 // indirect
 	gomodules.xyz/jsonpatch/v2 v2.1.0
-	gopkg.in/check.v1 v1.0.0-20200902074654-038fdea0a05b // indirect
+	gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b // indirect
 	k8s.io/api v0.19.7
 	k8s.io/apimachinery v0.19.7
 	k8s.io/client-go v0.19.7
 	k8s.io/code-generator v0.19.7
 	k8s.io/gengo v0.0.0-20201214224949-b6c5ce23f027 // indirect
 	k8s.io/klog v1.0.0
-	k8s.io/klog/v2 v2.5.0 // indirect
 	k8s.io/kube-openapi v0.0.0-20210113233702-8566a335510f
+	k8s.io/utils v0.0.0-20210111153108-fddb29f9d009 // indirect
 	knative.dev/pkg v0.0.0-20210127163530-0d31134d5f4e
 )